Forum Discussion
Difference between SSO under access policy and SSO in VPE
- Feb 12, 2024
The SSO profile attached to a access policy has 2 or 3 variables, session.sso.token.last.username and session.sso.token.last.password (and others, depending on the SSO profile).
These are not created by default in the VPE. The SSO credential mapping agent maps a username variable (most of the times session.logon.last.username, depending on what you select in the agent) into session.sso.token.last.username.
You could do the same in a variable assign agent, F5 has created the SSO credential mapping to help engineers and to show in the VPE your mapping SSO credentials.
So it is not mandatory.
I hope I makes it a bit more clear.
Cheers,
Kees
Correct, you need to modify the VPE. Default is start-> deny. Minimum is start -> allow.
You could use an SSO polixy/profile for this.
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com