Forum Discussion
Manipulate SAML assertion data
Here's an idea followed by some additional questions. On successful validation as the SP, the assertion content is actually stored in a session variable. I don't have it in front of me, but it's something like "session.saml.assertion". This is the decoded XML. So then there are a lot of options for what to do with that. And now the questions:
-
Do you need to send this assertion data as an actual (encoded) assertion, or maybe something simpler like an HTTP header?
-
If the former, do you need it in a POST request as the first request to the site and using a specific (potentially different) entityID/app URL?
-
If yes to 2, do you need to validate the internal SP's response?
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)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
