Hi @Marilee Turscak-MSFT,
I bumped into the same issue.
Registered redirect URLs:
When I specify
redirect_url=8000 the IDP redirects back to 8001, this is not expected behavior, the
redirect_url URL should be used.
The current behavior is [probably]:
- Verify that
redirect_url matches one of the registerd application URLs
- Select random
redirect_url out of the approved application URLs (probably the last)
- Redirect to URL selected by (2)
- Verify that
redirect_url matches one of the registered application URLs
- Redirect to URL specified in (1)
Rational: The application may run multi-instance or crash in which the port is already allocated, we would like to use port range in order to allow redundency/concurrency.
Please let me know if there is a better forum to discuss this.
You can still run the application if the reply URL doesn't match (not sure if that was what you were trying to do the first time).
"If I switch to IIS express on 43215 everything works without issue as well as if the port is totally ignored."
What exactly is your doubt?
this is not run, this is attempt to login.
please assume for a second that you may possibly be incorrect and read my test case, then explain it.
Thank you for clarifying. I wasn't trying to make an assumption but my product team contact wanted to confirmation from you - thanks for that!
In that case, you should not be able to sign in. Could you create a new application and try again? The issue may be exclusive to the current application.
I have tried 3 different app regs across 2 subscriptions with same results. They are all in same tennent
Sign in to comment