This message was deleted.
# citrix-netscaler
s
This message was deleted.
👀 1
k
So the problem is that if the attribute is empty, the attribute is "cut"? Seems like a bug, what release are you running?
It's a bit tricky to solve using nFactor, because the IDP stuff is not part of the flow and it's still going around the issue rather than having it working properly. I would likely check the attribute contents in nFactor and then the OAuth IdP policy expression would check if the attribute has a value and then the proper IdP policy would be applied for the user based on that, but you already did that?
m
I honestly think it is some kind of a bug cause I have a few - in my case SAML - IDP Implementations and there are often some attributes for some users empty and that never causes any issue with the saml Auth Response and I honestly thought that it would be the same with the OAuth IDP.
k
The SAML actions are totally different syntax-wise also. I don't really understand why the attributes in OAuth IdP action are set with that syntax, there are too many things that can go wrong (if they would instead have a clear attribute form similar to LDAP and SAML)?
m
yeah that would be great cause the syntax for oauth attributes is quite confusing. maybe just test it with one attribute that is empty and see if this causes the problem. maybe there is something else?
k
I bet it's just something no one has ran in to, or then it was fixed for some build and popped back
👍 1
j
Thanks for your input, was also wondering, as at the SAML-side it's way different than OAuth. It's a 13.0 Build. @Kari Ruissalo (WyW) I could check on the attribute contents in nFactor, but I can only use one IdP policy (limit on the SP-side) so that's the painpoint. Opened a case and waiting for a bug-confirmation or sth else
k
oh... that's correct, you're probably not able to use the user attributes for selecting the OAuth IdP policy/action, and even if you could, it wouldn't be too pretty.