Skip to content
This repository has been archived by the owner on Jul 31, 2024. It is now read-only.

Weird interaction behaviour when signing in. #228

Closed
Lutando opened this issue Aug 23, 2016 · 5 comments
Closed

Weird interaction behaviour when signing in. #228

Lutando opened this issue Aug 23, 2016 · 5 comments
Assignees
Labels
Milestone

Comments

@Lutando
Copy link
Contributor

Lutando commented Aug 23, 2016

I have a project that is almost identical to the Host project in this repository

However In my sample when I try to initiate implicit flow I get a mis-constructed redirect from the middleware. that looks sort of like this

http://localhost:5000/connect/login?returnUrl=http%3A%2F%2Flocalhost%3A5000%2Fconnect%2Fauthorize%2Flogin%3Fclient_id%3Dim...

for some reason its trying to route me to a controller/endpoint where the base route is /connect

There is hardly any noticeable difference in configuration between my project here and the host project linked above

Repro steps

  1. Get project as linked in this issue here.
  2. Run an implicit client like this one.
    2.1) Change app.js settings to the following:
  • authority: "http://localhost:5000",
  • client_id: "implicit_client",
  • scope: "openid api1",
  1. Run both solutions and try and login from the implicit client, and you will receive an odd redirect as mentioned above.
@Lutando
Copy link
Contributor Author

Lutando commented Aug 23, 2016

OK. well I found out the issue. The UserInteractionOptions.* specified in the options builder has to have a leading slash or you will run into the issue as described above.

@Lutando Lutando changed the title Wierd interaction behaviour when signing in. Weird interaction behaviour when signing in. Aug 23, 2016
@leastprivilege leastprivilege added this to the RC1 milestone Aug 24, 2016
@Lutando
Copy link
Contributor Author

Lutando commented Aug 24, 2016

I guess a bug fix would be to EnsureLeadingSlash() on set;

@brockallen
Copy link
Member

Yea, we'll figure something out. thanks for the report.

@brockallen
Copy link
Member

I think we will solve this via documentation. For now this was done in code comments, but when the proper documentation is written it will also be included in there. Thanks.

@lock
Copy link

lock bot commented Jan 15, 2020

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Jan 15, 2020
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