-
Notifications
You must be signed in to change notification settings - Fork 124
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
Non interactive user auth #68
Comments
I realize this is a year old and I hope you managed to solve your problem. We had the same issue and it caused quite a bit of problem when MFA and secure model got adopted as we needed each of our employees to authorize every request we were automating. We solved this by having a user authorize once, storing their token in the Azure Key Vault then having the refresh token used to keep doing automated tasks to the partner center in the background. This describes the process we followed hope it helps for others! |
Have you figure out how to change the console app sdk to be non interactive? Could you share how you did it? |
I have give up and just generate a token/refresh token manually first time. Then I have stock the access token/refresh token in a SQL table and my app update theses tokens automatically when they expire. A proper solution may exists but I don't found |
Feature Request
Maybe I have missunderstand the SecureAppModel and what I looking for is already existing. The year before, when MFA was not mandatory, I could use User Auth by directly getting access token with user credential like this :
It was so simple, now, since arround october I can't use my
GetUserToken
function becauseresponse.IsSuccessStatusCode
is false.My application is an API that allow our customer's users to do actions on partner centers like : listing there users account and add/remove licence on user account.
For this, application auth is not sufficient, so I have to use User Auth. I want to use a service account that auto-login in background as before. Is there any solution ?
The text was updated successfully, but these errors were encountered: