Syspass: Feature Request: oauth support

Created on 20 Feb 2017  路  7Comments  路  Source: nuxsmin/sysPass

@nuxsmin, what about login by oauth tokens?

kinfr kinquestion

Most helpful comment

@volands sorry for the late reply...

I've just released v3.1 because many bug fixes had to be performed and a major upgrade of plugins management that was needed to be done because a wrong implementation.

Although I'll need to find out how to deal with master password implementation and Oauth, I think it might be achieved in next release, that is v3.2, which would be ready in 6 months. That is a rough timeline, though I really think it would be almost a real release cycle.

@yahya09 that being said, I'm committed to implement Oauth on sysPass

Regards

All 7 comments

Nice, it would be an interesting feature for the next release.

Thanks for the feedback!

Already got it working with DUO. They have an LDAP authenticator that allows direct integration without code changes. I even have internal and external configurations that only required the touch authentication externally. I believe vasco and RSA have similar LDAP integrator.

Hi @nuxsmin!

Oauth would be very interesting for us - and I could imagine also for (a lot of) other people.

This issue here seems to be not active for longer time, but I noticed that the feature request is included in "sysPass 3.x Roadmap" (https://github.com/nuxsmin/sysPass/issues/422) but was not accomplished in the (now closed) 3.0 milestone (https://github.com/nuxsmin/sysPass/milestone/5) - and it is also currently not listed in (open) newer milestones (3.1, 3.2).

Only as short question in this context: do you already have a (rough) timeline for implementation respectively can you estimate if/when this feature will be included in syspass?

I also look for Oauth2 support for login method. Does anyone know if maybe someone has implemented it but not yet merged?
If not, I would like to try implementing it and maybe send PR when I'm done.

@volands sorry for the late reply...

I've just released v3.1 because many bug fixes had to be performed and a major upgrade of plugins management that was needed to be done because a wrong implementation.

Although I'll need to find out how to deal with master password implementation and Oauth, I think it might be achieved in next release, that is v3.2, which would be ready in 6 months. That is a rough timeline, though I really think it would be almost a real release cycle.

@yahya09 that being said, I'm committed to implement Oauth on sysPass

Regards

I see that oauth has been in to do since 2017, is there any progress on this implementation?

This feature would be a great for us too !
I might be able to help if you can give le a few guidelines on the auth process / how you would implement the feature.

Was this page helpful?
0 / 5 - 0 ratings