-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Initial login fails #10
Comments
In order to get more info, attach the Visual Studio debugger to the IIS process and set some breakpoints in: https://github.com/jakobadam/RDSFactor/blob/master/web/RDWeb/Pages/en-US/login.aspx |
On the "first" login typically the user have not entered a direct URL to the login page, but something shorter. So they will have been redirected and ReturnUrl is set when they reach the login page. The problem is that with ReturnUrl set the login page fails to set some session variables that the tokenform requires, so the tokenform will trigger a logoff, which redirects back to login - but without ReturnUrl set, so now it will work if the user tries again. I've fixed this in my fork: |
Awesome:) |
This is also a issue for me, when will @oskarb fix be merged into a new release? |
@chrisbbe Jakob have signaled that he's not maintaining any more. Feel free to use my fork instead, which contains a bunch of other fixes too. Some more are coming within a few days, just want to test them first. |
@chrisbbe If you do switch over, beware that I've made some incompatible changes to the configuration file. Look in the sample RDSFactor.ini for current syntax. I think the changes should be obvious. |
Ok, good to here that you want to continue the maintenance the project :D i will switch over as soon I find out how to build and package the source code. Have you considered to build, package and release versions the same way as in the original project? |
The first login to RD Web sometimes results in an error.
There is log output on the RADIUS server.
It always works the second time...
The text was updated successfully, but these errors were encountered: