npatel
Apprentice

Forms Based Auth page Redirects to same Login Page after Successful authentication

Jump to solution

Hello,

 

I recently upgraded to K2 5.2 from 4.7. I configured FBA site with all the references as mentioned in documentation.

 

Now authentication is successful when I login. (I checked logs in DB that it is successful.)

 

Ideally it should have been redirect to next page. But it remains on the same page.

Also it does not show any error in console or on page.

 

8507i4FF13CBE3F4B79DC.png

 

Can you tell me where am I missing?

 

Thanks,

Nirav

0 Kudos
Reply
3 Replies
Perc
Apprentice

Re: Forms Based Auth page Redirects to same Login Page after Successful authentication

Jump to solution

Hi nPatel,


 


Thank you for your post, I would like to ask are you experiencing the same issue within all browsers such IE, firefox and chrome?


Have you tried to access via private browser mode (incognito) ?


When configuring FBA did you follow the documentation below:


 


https://help.k2.com/onlinehelp/k2blackpearl/icg/4.7/default.htm#Configure/SF/SF_Authentication.htm


 


Kind regards,


 


Percy

0 Kudos
Reply
npatel
Apprentice

Re: Forms Based Auth page Redirects to same Login Page after Successful authentication

Jump to solution

Hi Perc,

 

Yes. I tried in incognito each time. Restart K2Server, Claim services.

 

Yes. Have followed the steps. It was working fine in 4.7. The same steps I'm doing for 5.2 but it's not working.

 

//Nirav

0 Kudos
Reply
npatel
Apprentice

Re: Forms Based Auth page Redirects to same Login Page after Successful authentication

Jump to solution

Hi Perc,

 

We were able to identify the issue.

 

The issue was with the claim type under ‘Claims’. We had given https (like https://schemas.mi...). It should be http even if the site is https.

Correct ones:

http://schemas.microsoft.com/identity/claims/identityprovider

http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name

 

There were other errors which we were getting:

Invalid reply url for realm

- It was trying to authenticate with SharePoint even when we didn't configure SP auth; we only had custom security provider.

(not sure that these two errors were because of http, but logging here.)

 

After 'http' change - all solved.

 

Thank you.

Nirav

0 Kudos
Reply