-
Notifications
You must be signed in to change notification settings - Fork 87
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
API changes for GA release #380
Labels
Comments
This was referenced Feb 13, 2023
Merged
Merged
This is really misleading as it's not mentioned in the docs but this new format must be used for it to work. All the examples I could find were incorrect. |
Well, we GA-ed so I guess this can be closed. |
yiannistri
added a commit
to yiannistri/rancher
that referenced
this issue
Apr 10, 2024
…r-go to v1.2.2 and migrate code as per AzureAD/microsoft-authentication-library-for-go#380
yiannistri
added a commit
to yiannistri/rancher
that referenced
this issue
Apr 11, 2024
…r-go to v1.2.2 and migrate code as per AzureAD/microsoft-authentication-library-for-go#380
yiannistri
added a commit
to yiannistri/rancher
that referenced
this issue
Apr 11, 2024
…r-go to v1.2.2 and migrate code as per AzureAD/microsoft-authentication-library-for-go#380
yiannistri
added a commit
to yiannistri/rancher
that referenced
this issue
Apr 12, 2024
…r-go to v1.2.2 and migrate code as per AzureAD/microsoft-authentication-library-for-go#380
yiannistri
added a commit
to yiannistri/rancher
that referenced
this issue
Apr 15, 2024
…r-go to v1.2.2 and migrate code as per AzureAD/microsoft-authentication-library-for-go#380
yiannistri
added a commit
to yiannistri/rancher
that referenced
this issue
Apr 15, 2024
…r-go to v1.2.2 and migrate code as per AzureAD/microsoft-authentication-library-for-go#380
yiannistri
added a commit
to yiannistri/rancher
that referenced
this issue
Apr 15, 2024
…r-go to v1.2.2 and migrate code as per AzureAD/microsoft-authentication-library-for-go#380
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
API changes since v0.8.0
Upgrading from v0.8.* may require code changes as described below.
confidential.New
requires an authority #394confidential.WithAuthority
has been deleted, and the URL it set is now a parameter ofconfidential.New
:confidential.NewCredFromCertChain
replacesNewCredFromCert
#391If your application calls
NewCredFromCert
, update arguments and return values:before
after
If your application calls
confidential.NewCredFromCertChain
, callNewCredFromCert
instead.All methods accessing cache data have a
Context
parameter #378For example,
RemoveAccount
andAccounts
:Renamed functions
These functions are renamed but otherwise unchanged:
confidential.NewCredFromCertChain
->NewCredFromCert
#391confidential.WithAccessor
->WithCache
#386public/Client.CreateAuthCodeURL
->AuthCodeURL
#384Deleted API
confidential.NewCredFromAssertion
. This function was deprecated in v0.6.0; useconfidential.NewCredFromAssertionCallback
instead #385public.InteractiveAuthOption
andconfidential.AcquireTokenSilentOptions
. #383, #390confidential/Client.UserID
. The value was always""
and never used by the client. #389New
cache.ExportReplace
parametersThe interface for custom cache implementations has new parameters for
Context
and metadata (#378, #395).The text was updated successfully, but these errors were encountered: