You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a ServiceClientCredentials implementation that logins to our service on client creation, then stores to authentication credentials for subsequent requests. This worked fine with the old version
publicclassCustomLoginCredentials:ServiceClientCredentials{privatestringAuthenticationToken{get;set;}publicoverridevoidInitializeServiceClient<T>(ServiceClient<T>client){// make login request. save authentication token in AuthenticationToken}publicoverride Task ProcessHttpRequestAsync(HttpRequestMessagerequest,CancellationTokencancellationToken){// place AuthenticationToken in request header}}
So then declaring our client var client = new ClientAPI(new Uri("url"), new CustomLoginCredentials());
The InitializeMethod would get called and then all requests would be properly authenticated.
This does work any more in the new version. Please let me know if this is a bug (I could see into fixing it myself) or some new intended behavior.
The text was updated successfully, but these errors were encountered:
We have a ServiceClientCredentials implementation that logins to our service on client creation, then stores to authentication credentials for subsequent requests. This worked fine with the old version
So then declaring our client
var client = new ClientAPI(new Uri("url"), new CustomLoginCredentials());
The InitializeMethod would get called and then all requests would be properly authenticated.
This does work any more in the new version. Please let me know if this is a bug (I could see into fixing it myself) or some new intended behavior.
The text was updated successfully, but these errors were encountered: