Skip to content
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

Problem with autologin #14

Open
g3t0r opened this issue Feb 17, 2018 · 3 comments
Open

Problem with autologin #14

g3t0r opened this issue Feb 17, 2018 · 3 comments
Assignees

Comments

@g3t0r
Copy link

g3t0r commented Feb 17, 2018

Always when I run application, it's opening page in browser with Microsoft login page. The same behaviour with both auto login on and off. Should it be like that? I hope there is a way to login without any user interaction.

@isac322
Copy link
Owner

isac322 commented Feb 21, 2018

Because of auth policy of Microsoft(first diagram), there must be at least one user interaction.
But I found a library that support caching the signin info.
I think if caching saves its info into file, fallowing signin can be done silently for same user.
Another way is sdk provide signin url and user past the url into browser and copy resulting auth info from browser to terminal.

By the way, name of autoLogin parameter is my mistake. What I meant was actually 'construct with signin'. I think I should change the name. 😢

@isac322 isac322 self-assigned this Feb 21, 2018
@leandre84
Copy link

+1

Persisting and setting the refresh token should do the trick, however, getRefreshToken() on the Client instance always returns null in my environment (maybe it's related to OneDrive Business which I'm using?).

@timoage
Copy link

timoage commented Jul 3, 2018

Hey Isac,
are you planning to implement sign-in with refreshToken? Because not having it would mean a show stopper for me

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants