Skip to content
This repository has been archived by the owner on Sep 18, 2021. It is now read-only.

Endless loop while manually triggering Identity Server logout Url from Browser History? #3857

Open
1 task
mrbbm opened this issue Sep 15, 2017 · 2 comments
Open
1 task
Labels

Comments

@mrbbm
Copy link

mrbbm commented Sep 15, 2017

  • I read and understood how to enable logging

Question / Issue

I'm having a question, I got a Logout URL from the Browsers History

https://localhost:2025/core/login?signin=a84e5846c781b2bf63619efb97a76b43

The testing team traced this URL and tried to trigger, its causing endless redirects, whats the logic behind in this ? How to fix this ?

Moreover, in the Browsers history, we found the Login URL, it simply shows a blank screen

https://localhost:2025/core/login?signin=a84e5846c781b2bf63619efb97a76b43

How to handle these session-less URL's ?

Kindly assist me in this regards.

@mrbbm mrbbm changed the title Endless loop while manually triggering Identity Server logout Url ? Endless loop while manually triggering Identity Server logout Url from Browser History? Sep 15, 2017
@brockallen
Copy link
Member

We provide a URL to redirect the user to when the signin message is no longer valid: InvalidSignInRedirectUrl: https://identityserver.github.io/Documentation/docsv2/configuration/authenticationOptions.html

@IncRev-Bala
Copy link

Its because, in the custom view the page element will have NULL value. Kindly ensure the page property has any value, if TRUE, load that page otherwise redirect to any custom error page.

protected virtual Task<Stream> Render(CommonViewModel model,string page,string clientId = null) 
{
    if (string.IsNullOrWhiteSpace(page)) {
        page = "Error";   // Custom Error message View
    }

    // Rest of the code .......
}

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants