ComponentSpace

Forums



Getting issue in while authenticating SAML response with OKTA


Getting issue in while authenticating SAML response with OKTA

Author
Message
alokratn
alokratn
New Member
New Member (4 reputation)New Member (4 reputation)New Member (4 reputation)New Member (4 reputation)New Member (4 reputation)New Member (4 reputation)New Member (4 reputation)New Member (4 reputation)New Member (4 reputation)

Group: Awaiting Activation
Posts: 3, Visits: 6
Hi Team,

We are using ComponentSpace.SAML2 DLL  libraries for SSO authentication in one of the MVC based WEB application. 

Currently we are using One login(SSO) as IDP and we are planning to move to OKTA(SSO) as IDP.
For this purpose we are testing it first with OKTA after configuring required changes related to SP metadata and IDP metadata.

We are facing one issue while receiving and processing the SAML assertion contained in the SAML response from OKTA(IDP) after logging into the OKTA SSO portal.
We are getting below exception at this method :
 
Method: SAMLServiceProvider.ReceiveSSO(Request, out isInResponseTo, out partnerIdP, out loginUserEmail, out attributes, out targetUrl);

Exception type: SAMLBindingException
Exception message: The message is not an HTTP POST.

Please help us in tracking what will be the possible reason for this error.

Thanks & Regards,
Alok Kumar Pandey


ComponentSpace
ComponentSpace
ComponentSpace Development
ComponentSpace Development (4.4K reputation)ComponentSpace Development (4.4K reputation)ComponentSpace Development (4.4K reputation)ComponentSpace Development (4.4K reputation)ComponentSpace Development (4.4K reputation)ComponentSpace Development (4.4K reputation)ComponentSpace Development (4.4K reputation)ComponentSpace Development (4.4K reputation)ComponentSpace Development (4.4K reputation)

Group: Administrators
Posts: 3.2K, Visits: 11K
Hi Alok
You'll find our Okta Integration Guide at:
https://www.componentspace.com/Forums/5439/Okta-Integration-Guide
The SAML response from the IdP will be received in an HTTP Post.
It sounds like your assertion consumer service endpoint is receiving something other than an HTTP Post.
It's unlikely this is coming from Okta.
I suggest using the browser developer tools to capture the network traffic.
Take a close look at the flow once login at Okta completes.
You should see an HTTP Post to your assertion consumer service endpoint.
If you're seeing an HTTP Get etc, the network traffic capture should help to identify the cause.



Regards
ComponentSpace Development
alokratn
alokratn
New Member
New Member (4 reputation)New Member (4 reputation)New Member (4 reputation)New Member (4 reputation)New Member (4 reputation)New Member (4 reputation)New Member (4 reputation)New Member (4 reputation)New Member (4 reputation)

Group: Awaiting Activation
Posts: 3, Visits: 6
ComponentSpace - 4/25/2019
Hi Alok
You'll find our Okta Integration Guide at:
https://www.componentspace.com/Forums/5439/Okta-Integration-Guide
The SAML response from the IdP will be received in an HTTP Post.
It sounds like your assertion consumer service endpoint is receiving something other than an HTTP Post.
It's unlikely this is coming from Okta.
I suggest using the browser developer tools to capture the network traffic.
Take a close look at the flow once login at Okta completes.
You should see an HTTP Post to your assertion consumer service endpoint.
If you're seeing an HTTP Get etc, the network traffic capture should help to identify the cause.


Hi Team,

We have checked the case as you suggested and see, we already getting the SAML assertion response in Http POST, so please requesting you to suggest for the next.


Thanks & regards,



ComponentSpace
ComponentSpace
ComponentSpace Development
ComponentSpace Development (4.4K reputation)ComponentSpace Development (4.4K reputation)ComponentSpace Development (4.4K reputation)ComponentSpace Development (4.4K reputation)ComponentSpace Development (4.4K reputation)ComponentSpace Development (4.4K reputation)ComponentSpace Development (4.4K reputation)ComponentSpace Development (4.4K reputation)ComponentSpace Development (4.4K reputation)

Group: Administrators
Posts: 3.2K, Visits: 11K
After the HTTP Post, do you see any HTTP Gets etc to the same URL?
If there's still an issue, please save the browser network traffic to an HAR file and send this to [email protected] mentioning your forum post.

Regards
ComponentSpace Development
alokratn
alokratn
New Member
New Member (4 reputation)New Member (4 reputation)New Member (4 reputation)New Member (4 reputation)New Member (4 reputation)New Member (4 reputation)New Member (4 reputation)New Member (4 reputation)New Member (4 reputation)

Group: Awaiting Activation
Posts: 3, Visits: 6
ComponentSpace - 4/26/2019
After the HTTP Post, do you see any HTTP Gets etc to the same URL?
If there's still an issue, please say the browser network traffic to an HAR file and send this to [email protected] mentioning your forum post.

Yes, after the HTTP Post, we are getting response in HTTP GET witht the same URL.
ComponentSpace
ComponentSpace
ComponentSpace Development
ComponentSpace Development (4.4K reputation)ComponentSpace Development (4.4K reputation)ComponentSpace Development (4.4K reputation)ComponentSpace Development (4.4K reputation)ComponentSpace Development (4.4K reputation)ComponentSpace Development (4.4K reputation)ComponentSpace Development (4.4K reputation)ComponentSpace Development (4.4K reputation)ComponentSpace Development (4.4K reputation)

Group: Administrators
Posts: 3.2K, Visits: 11K
Ok. You need to determine why you're receiving the HTTP Get.
It won't be coming from Okta so it's most likely coming from your application.
The browser developer tools should show you the flow between receiving the SAML response from Okta in an HTTP Post and receiving the HTTP Get.  



Regards
ComponentSpace Development
GO


Similar Topics


Execution: 0.000. 2 queries. Compression Enabled.
Login
Existing Account
Email Address:


Password:


Select a Forum....












Forums, Documentation & Knowledge Base - ComponentSpace


Search