-
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
OAuth Login #409
Comments
Oh, I'm afraid this is not implemented :/ Currently you'd need to login via web and extract the session token. |
Thanks for the info it at least brings me the peace of mind it's not me! I've a feature request... :) Is there a way to increase the validity of the session token? I was doing that, but at the moment it is only 30sec (?) which is not enough to do anything, and I'm sometimes even to slow to extract it from the developer console in the browser and copy it to my Terminal. |
No it's not you :) Doing this openid stuff is a bit of a hassle to implement, but that should absolutely be done at some point. You can for now extends the session token validity in the config file, look for
Then dsc should get a new token automatically once this one is close to expire (obviously, adopt as necessary). |
I can imagine :( Oh is it 5min? Mine started to invalidate very fast, although I'm not sure if I didn't set it lower in the config and I can't check at the moment- Anyway thanks for the idea, I'll try that! |
Hey,
I'm not sure if this is really an issue or I'm not seeing something obvious. My docspell instance has OAuth as the only way to login, hence the users are not "local" users and don't have a password. So I have the same problem with both the API and DSC: I can't login, since I can't give a password. And also not a session token, because I would need to login to get one.
I've also read through the source code a bit, but didn't get far.
Any help would be appreciated :)
Sebastian Elisa
The text was updated successfully, but these errors were encountered: