18
Views
7
Comments
[Microsoft Login Connector - Traditional Web] Single sign on using microsoft login connector in traditional web app
Application Type
Traditional Web

Hi Everyone ,
I have implemented SSO using microsoft login connector - Traditional web in one of SQL application which traditional web app.

I have follow the document and register application on the azure portal and provided appropriate callback page url as suggested in the documents.

But after succesfully authorisation from the azure endpoint (portal) from the callback page of the forge component (Connector) I am not able to redirected to SQL application Homepage.

I have checked sign in logs in azure portal all looks fine as well have checked the error log in the service center. There are no errors currently logged regarding the issue.

After authorisation I am not able to redirect to the SQL app homepage from the callbackpage. I am stuck here in my implementation. For your reference I am attaching the OML files. Please suggest me If I miss something in the implementation.

Below is the implementation in SQL app.

Callback page preparation code.


After authentication getting blank screen only and unable to redirect on the request page from the SQL Application.


Please suggest me how can I resolve this issue ?

MicrosoftLoginConnector.oml
SQL.oml
2025-04-17 05-42-16
Ajit Kurane

There was a little bug in callback page of the component. After that I tried to login and I got below error in service center logs. Please suggest me which change I need to do resolve this error in above code.

Thanks.

2019-07-01 07-16-04
Vinod Patidar

Hi Ajit,

Could you please check your browser console for any error details? Additionally, you can debug the MicrosoftLoginConnector CallbackPage.aspx to identify any errors or exceptions on that page. 

Thanks

Vinod

2025-04-17 05-42-16
Ajit Kurane

Hi Vinod,

I have attached the error log from service center. After debugging also I will see if its giving any error details in local variabls.

Thanks.

2025-04-17 05-42-16
Ajit Kurane

Hi Vinod,

In the debugging I found below error,

"AADSTS54005: OAuth2 Authorization code was already redeemed, please retry with a new valid code or use an existing refresh token. Trace ID: 7b92c659-5a66-4fdc-91e2-582234d5db00 Correlation ID: 74fa25bf-b636-4927-b646-7e0973a53a20 Timestamp: 2025-01-30 14:50:31Z"

How can I implement solution for this in the above oml files ?

Thanks.

2025-04-17 05-42-16
Ajit Kurane

@Miguel Amado @Vincent Koning @Daniël Kuhlmann 

Please suggest me any work around I need to implement to resolve the above error.

Thanks.

2025-04-17 05-42-16
Ajit Kurane

Hi All,

Is there any solution for the mentioned error?

Thanks 

2025-04-17 05-42-16
Ajit Kurane

Hi All,

Can anyone have solution to resolve this issue?

Thanks 

Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.