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
{{ message }}
This repository has been archived by the owner on Aug 29, 2018. It is now read-only.
If discoverUserRegistered is called and no user information was found, i.e. registry returns with "No information could be found", the IdentityManager should not return this string, and instead either reject the promise or resolve it without anything.
In the code I see that the IdentityManager doesn't check the message code when handling the reply, which might be the reason for this problem. However, if the registry returns the string "No information could be found" with the code 200, it should be changed to use an error code in such case instead.
The text was updated successfully, but these errors were encountered:
If discoverUserRegistered is called and no user information was found, i.e. registry returns with "No information could be found", the IdentityManager should not return this string, and instead either reject the promise or resolve it without anything.
In the code I see that the IdentityManager doesn't check the message code when handling the reply, which might be the reason for this problem. However, if the registry returns the string "No information could be found" with the code 200, it should be changed to use an error code in such case instead.
The text was updated successfully, but these errors were encountered: