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
Enhancement: Develop password migration mode for PTA plugin #1813
Comments
Comment from nhosoi (@nhosoi) at 2016-03-11 06:33:11 Per triage, setting the milestone to 1.3.6. If necessary, we should add the notes to password-migration-design.html? |
Comment from nhosoi (@nhosoi) at 2017-02-11 22:53:16 Metadata Update from @nhosoi:
|
Comment from mreynolds (@mreynolds389) at 2017-05-08 22:06:35 Metadata Update from @mreynolds389:
|
Comment from mreynolds (@mreynolds389) at 2017-07-05 18:00:24 Metadata Update from @mreynolds389:
|
Comment from mreynolds (@mreynolds389) at 2017-10-18 22:04:22 Metadata Update from @mreynolds389:
|
@Firstyear - is this RFE still useful? Winsync is going away eventually... |
Not really, I think we can close it. Do we have a timeline of when we plan to remove winsync? We have a few customers using it at SUSE and I'm happy to take over "some" of it in a narrow scope. Maybe we can email about this? |
There is no time line, but management's stance is that using Trusts is preferred over winsync. It's not going away in 2.x, but maybe in 3.x it will be deprecated? We just don't want to maintain it forever. |
@mreynolds389 I'll email you about it :) |
Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/48753
http://directory.fedoraproject.org/docs/389ds/design/password-migration-design.html
This details a migration mode which will capture and store a password on successful auth. We don't currently have this, so we should develop and enable it.
The text was updated successfully, but these errors were encountered: