SecureAuth IdP Version affected: All
Description:
Description:
This KB article will show what Oidctoken.aspx needs to receive in order to give out a token using a Grant Type of Authorization_code
Cause:
NA
Resolution:
Grant_Type Authorization_Code
1. First you need to get an Authorization_code. This is generated by going to SecureAuth.aspx in a browser with the correct parameters. Here is an example
https://awood.example.com/secureauth8/secureauth.aspx?response_type=code&client_id=dcf4f0410d26XXXXXX1642e443f12dad&redirect_uri=https%3A%2F%2Flogin.example.com%
scope=openid+offline_access&state=CAAAAWFwTWJiME8wMFkwMDAwMDA0Qzk0AAAA1Dv-
2. Post to https://youridp.example.com/secureauthxx/oidctoken.aspx
3. Needs to be x-www-form-urlencoded
4. Should contain the following
grant_type: authorization_code
code: The code retrieved in step1
client_id: The client id set in the post auth page
client_secret: The client secret set in the post auth page
scope: openid and any others you need
redirect_uri a valid redirect uri as set in the post auth page of the realm
1. First you need to get an Authorization_code. This is generated by going to SecureAuth.aspx in a browser with the correct parameters. Here is an example
https://awood.example.com/secureauth8/secureauth.aspx?response_type=code&client_id=dcf4f0410d26XXXXXX1642e443f12dad&redirect_uri=https%3A%2F%2Flogin.example.com%
scope=openid+offline_access&state=CAAAAWFwTWJiME8wMFkwMDAwMDA0Qzk0AAAA1Dv-
2. Post to https://youridp.example.com/secureauthxx/oidctoken.aspx
3. Needs to be x-www-form-urlencoded
4. Should contain the following
grant_type: authorization_code
code: The code retrieved in step1
client_id: The client id set in the post auth page
client_secret: The client secret set in the post auth page
scope: openid and any others you need
redirect_uri a valid redirect uri as set in the post auth page of the realm
SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.
Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.
Comments
Please sign in to leave a comment.