vxq9g (vxq9g) asked a question.
template app 3 Fields
Hi all,
I am trying to setup SSO for an app which requires the employee number in addition to the username to login. I set it up with "Template app 3 Fields".
My issue is with the "Extra Field Value". I can't seem to figure out how to make this field dynamic. When I hardcode my own employee number in the Extra Field Value and try to connect it works fine but that's obviously not what I want. I tried using the okta variables (i.e. user.EmployeeNumber) with or without enclosing it in '${}' but with no luck.
Is there a way to map the "Extra Field Value" to an Okta attribute or to an app attribute? If not, how would I setup a custom sso with an extra fields which value changes for every user?
Hi Benjamin,
For SWA flows, the 3rd field is not supported for dynamic value parsing, the filed can only work with static values from the initial configuration and will be using this static value on all accounts assigned, this is covered in the documentation for the Template config, you can find it on our help side under the "Configure the Okta Template App and Okta Plugin Template App"
In the section of this article "Cases where the Template Plugin App will not work" there is this exact use case :
Require a parameter beyond just username and password, as they can use Template Plugin App 3 Fields if the parameter is static and doesn't change
In this situation you would need to work out another SSO method for the SP, the SWAP flow is not supported as detailed with your requirements for the dynamic 3rd field, if there is a SAML option available you can pursue that avenue.
If you need any additional info or assistance, just open a case with our Support Department.