-
Notifications
You must be signed in to change notification settings - Fork 22
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
did:web resolver should allow resolving DIDs that have different domain in DID if configured #1475
Comments
@troyronda Any opinion on this? |
sandrask
changed the title
Should did:web resolver allow resolving DID that has different domain in did web ID
did:web resolver should limit resolving DIDs that has different domain in did web ID if configured
Sep 15, 2022
As per discussing with @troyronda we should limit resolving did:web DIDs to those with hosting domain in DID (or configured additional domains) |
sandrask
changed the title
did:web resolver should limit resolving DIDs that has different domain in did web ID if configured
did:web resolver should allow resolving DIDs that have different domain in DID if configured
Sep 15, 2022
sandrask
added a commit
to sandrask/orb
that referenced
this issue
Sep 15, 2022
…t domain in DID if configured Limit resolving did:web DIDs to those with hosting domain in DID (or configured additional domains) Closes trustbloc#1475 Signed-off-by: Sandra Vrtikapa <sandra.vrtikapa@securekey.com>
sandrask
added a commit
to sandrask/orb
that referenced
this issue
Sep 15, 2022
…t domain in DID if configured Limit resolving did:web DIDs to those with hosting domain in DID (or configured additional domains) Closes trustbloc#1475 Signed-off-by: Sandra Vrtikapa <sandra.vrtikapa@securekey.com>
sandrask
added a commit
to sandrask/orb
that referenced
this issue
Sep 15, 2022
…t domain in DID if configured Limit resolving did:web DIDs to those with hosting domain in DID (or configured additional domains) Closes trustbloc#1475 Signed-off-by: Sandra Vrtikapa <sandra.vrtikapa@securekey.com>
sandrask
added a commit
to sandrask/orb
that referenced
this issue
Sep 15, 2022
…t domain in DID if configured Limit resolving did:web DIDs to those with hosting domain in DID (or configured additional domains) Closes trustbloc#1475 Signed-off-by: Sandra Vrtikapa <sandra.vrtikapa@securekey.com>
sandrask
added a commit
to sandrask/orb
that referenced
this issue
Sep 16, 2022
…t domain in DID if configured Limit resolving did:web DIDs to those with hosting domain in DID (or configured additional domains) Closes trustbloc#1475 Signed-off-by: Sandra Vrtikapa <sandra.vrtikapa@securekey.com>
sandrask
added a commit
to sandrask/orb
that referenced
this issue
Sep 16, 2022
…t domain in DID if configured Limit resolving did:web DIDs to those with hosting domain in DID (or configured additional domains) Closes trustbloc#1475 Signed-off-by: Sandra Vrtikapa <sandra.vrtikapa@securekey.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For example if the request to resolve did:web:orb.domain3.com:scid:suffix was sent to https://orb.domain1.com/sidetree/v1/identifiers should we resolve the DID if we have it (due to propagation we may have DID with that suffix)
As per discussing with @troyronda we should limit resolving did:web DIDs to those with hosting domain in DID (or configured additional domains)
The text was updated successfully, but these errors were encountered: