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
Hydra should ship a default/exemplary identity provider using postgres located here. Identity providers must implement an HTTP REST interface with (at least) the following capabilities:
Mandatory (used by Hydra):
GET /identities: Should return all known identities. Should support pagination.
GET /identities/<id>: Should return an identities information
POST /authenticate: Should return an identitiy if valid credentials are given. Question: What to support id/password, username/password, email/password, ... ?
Recommended: Not used by Hydra but useful in a real world scenario:
POST /identities: Should create a new user
DELETE /identities/<id>: Should delete a user
PUT /identities/<id>/password: Should update the identities password
Optional features:
Password reset
... ?
Identities should be sent using JSON:
{
"id": "12341234" // mandatory
// ...
}
Errors should be sent using the HTTP status header and a JSON message:
This will be part of #62
I want hydra to be able to maintain a list of identity providers which can be added and removed using the CLI:
Hydra should ship a default/exemplary identity provider using postgres located here. Identity providers must implement an HTTP REST interface with (at least) the following capabilities:
Mandatory (used by Hydra):
GET /identities
: Should return all known identities. Should support pagination.GET /identities/<id>
: Should return an identities informationPOST /authenticate
: Should return an identitiy if valid credentials are given. Question: What to support id/password, username/password, email/password, ... ?Recommended: Not used by Hydra but useful in a real world scenario:
POST /identities
: Should create a new userDELETE /identities/<id>
: Should delete a userPUT /identities/<id>/password
: Should update the identities passwordOptional features:
Identities should be sent using JSON:
Errors should be sent using the HTTP status header and a JSON message:
For inspiration check out the current account module
The text was updated successfully, but these errors were encountered: