-
Notifications
You must be signed in to change notification settings - Fork 57
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
Kerberos authentication with autorest v3 #944
Comments
Hey @SkinnySackboy , from v2 -> v3 we don't use I'm not sure the best way for you to switch since |
Hi @SkinnySackboy ! We don't have any plan to port this feature to our new SDK. It was added by an external contributor to msrest, and we were happy to accept the contribution and ship it, but we don't have it on our new backlog. That being said, the code to make it work is really simple, see this line: If you control the Let us know if it works or if we can do anything. We're open to contribution, if you want to port Kerberos to the new architecture :) |
Thanks @lmazuel we'll try that and let you know how it goes. Thanks again. |
@SkinnySackboy are you ok if I close this issue? thanks! |
Yes thanks @iscai-msft thanks again for your help, much appreciated. |
We would like to upgrade from autorest v2 to v3, but we are running into trouble keeping our existing mechanism to use Kerberos authentication (the web service is hosted on IIS and allows users to log in with their windows active directory credentials).
This is what we were doing with v2.
Is anyone aware of what the equivalent might be for v3 please, as when we generate the API it seems to be expecting a credential of type
azure.core.credentials.TokenCredential
?Thanks in advance.
The text was updated successfully, but these errors were encountered: