Bug #34568
closed
rsaauth can not be used multiple times on one page
Added by Alexander Stehlik over 12 years ago.
Updated about 7 years ago.
Description
When using rsaauth for the felogin extension it is not possible to have another login form on the same page that also uses rsaauth for encrypting the user/password data.
As far as I can see there are two possible solutions:
- the storage need to be able to store multiple key pairs (at the moment only one key pair can be stored)
- if a key pair is generated it needs to be stored in a static variable so that it can be used in other forms
Please let me know if I can help out with a patch for this.
- Status changed from New to Needs Feedback
- Assignee set to Steffen Ritter
Steffen, you are probably the right one to say if this is feasible. Or if there are other things to consider.
- Status changed from Needs Feedback to Accepted
- Assignee deleted (
Steffen Ritter)
Yes, know this behaviour - I think in the second way would fit better...
Please make also sure the javascript files for the encrypting will be added only one time.
Since the next release of sr_feuser_register (3) will ship with support for salted_passwords and rsa encrypted passwords (and adds conflict status with kb_md5fepw), i think it will be pretty common to have rsa protected login form and the password fields on the same page.
Identifying this problem took quite some time and although there is (now) a note and a link in the sr_feuser_register documentation regarding this error, this should be fixed for the next releases IMHO.
What is the current state of this Issue?
The same problem exists in TYPO3 5.2.x, e.g. with sr_feuser_register 3.1.x
- Assignee set to Nicole Cordes
- Target version set to 7.4 (Backend)
- Is Regression set to No
- Status changed from Accepted to Under Review
Patch set 8 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/40938
Patch set 9 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/40938
Patch set 10 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/40938
Patch set 11 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/40938
Patch set 12 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/40938
Patch set 13 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/40938
Patch set 14 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/40938
Patch set 15 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/40938
Patch set 16 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/40938
Patch set 17 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/40938
Patch set 18 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/40938
Patch set 19 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/40938
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
- Status changed from Resolved to Closed
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by