Bug #46022
closed
login with openId-authentication
0%
Description
When a I try to login to the Typo3-backend with a openid, then this works only for the second time.
That's what happens:
- go to the backend login site
- enter the openid and press enter
- site is redirected to the provider
- "enter your credentials" and press enter
- site is redirected to the backend login site, but no login is performed
Here you have to enter the openid a second time and press enter again; the second time it's working... But the login should work for the first time.
Additional infos:
- Typo3 6.0.2 (updated from 4.7)
- PHP 5.3.8
- Hosted on IIS
- Tested with Firefox 19 and IE10
- Openid-Provider: www.clavid.ch (Google doesn't works today)
Updated by Stefan Galinski over 11 years ago
- Category changed from 1134 to Authentication
Updated by Ekkehard Gümbel over 10 years ago
This seems to be a problem specifically with Clavid, as I did not run into it with other OpenID providers.
In detail:
- In 4.5.32, I experienced the same behavior as reported
- In 6.1.7, OpenID login with Clavid seems to be broken entirely
Cheers,
Ekke
P.S. Why was the category changed to "saltedpasswords/rsaauth"?
Updated by Ekkehard Gümbel over 10 years ago
Same behavior with 4.7.17.
To be 100% clear, let me give the exact sequence of action:- Make sure you are logged OFF from Clavid
- Go to the TYPO3 backend and give it your Clavid OpenID
- Clavid will ask you to log on, which you do
- TYPO3 will now claim "logon failed"
- Repeat (2)
- Without further interaction, you are now successfully logged on to TYPO3
Updated by Helmut Hummel over 9 years ago
- Category changed from Authentication to 1134
- Is Regression set to No
Updated by Markus Klein over 9 years ago
- Status changed from New to Needs Feedback
- Assignee set to Markus Klein
Is this still an issue with TYPO3 6.2 or 7.4?
Updated by Wouter Wolters about 9 years ago
- Status changed from Needs Feedback to Closed
No feedback within the last 90 days => closing this issue.
If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.