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
The public API for authentication is currently separated into 2 parts:
Authenticate
ParseAuthenticationResponse
Consumers of the authn-client library currently need to first call the Authenticate method, get the output and call the method ParseAuthenticationResponse with it. This adds redundant complexity to the flow and can be reduced easily by letting the Authenticate method perform the whole flow by itself, so that consumers can call one method without the need of another.
So, instead of performing the following:
resp, err := authn.Authenticate()
if err != nil {
// Do something
}
err = authn.ParseAuthenticationResponse(resp)
if err != nil {
// Do something
}
consumers can perform the following:
err := authn.Authenticate()
if err != nil {
// Do something
}
The text was updated successfully, but these errors were encountered:
The public API for authentication is currently separated into 2 parts:
Authenticate
ParseAuthenticationResponse
Consumers of the authn-client library currently need to first call the
Authenticate
method, get the output and call the methodParseAuthenticationResponse
with it. This adds redundant complexity to the flow and can be reduced easily by letting theAuthenticate
method perform the whole flow by itself, so that consumers can call one method without the need of another.So, instead of performing the following:
consumers can perform the following:
The text was updated successfully, but these errors were encountered: