Web API: saml2/acs: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 4: | Line 4: | ||
Url: POST /api/samlsignin | Url: POST /api/samlsignin | ||
Content-Type: application/x-www-form-urlencoded | Content-Type: application/x-www-form-urlencoded | ||
Body: (as form data with SAMLResponse) | Body: (as form data with "SAMLResponse" property) | ||
SAMLResponse=<assertiondata> | SAMLResponse=<assertiondata> | ||
</pre> | </pre> | ||
Revision as of 23:11, 5 October 2021
Samlsignin accepts the SAML assertion from an identity provider (IdP) and responses with the HTTP status code 302 (Found) with a location (in HTTP response header) to QPR ProcessAnalyzer containing samlhash as a parameter in the the location (that is then used to login).
Url: POST /api/samlsignin Content-Type: application/x-www-form-urlencoded Body: (as form data with "SAMLResponse" property) SAMLResponse=<assertiondata>
Example location (in the HTTP response header): https://customer.onqpr.com/qprpa/ui/#?sys:username=<username>&sys:samlhash=<samlhash>