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 Jan 31, 2023. It is now read-only.
In our v1.0.19 release, we broke the ability to add an identity to a wallet, by connecting to the gateway and providing an enrollment ID and secret.
This is also exposed when you create a new wallet (and it follows the same flow).
What happens is that if you add a gateway, and try to use it, then it doesn't appear in the list of gateways to use.
Expected Behavior
The gateway doesn't show up in the list of gateways to connect to.
Actual Behavior
We should see all gateways and be able to use them to enroll with,
Description
In our v1.0.19 release, we broke the ability to add an identity to a wallet, by connecting to the gateway and providing an enrollment ID and secret.
This is also exposed when you create a new wallet (and it follows the same flow).
What happens is that if you add a gateway, and try to use it, then it doesn't appear in the list of gateways to use.
Expected Behavior
The gateway doesn't show up in the list of gateways to connect to.
Actual Behavior
We should see all gateways and be able to use them to enroll with,
Possible Fix
Steps to Reproduce
Existing issues
Log File
Your Environment
The text was updated successfully, but these errors were encountered: