fyi.opensocial.getAuthorization
An app's pending request to sign in as a group, as the caller would approve it: the app, the groups the caller may act for, and for each one what the caller's roles let the app do. Called by the console's approval page, with service auth from the caller's own PDS.
Details · query
| Kind | query |
|---|---|
| Authority | opensocial.fyi |
| Indexed |
Showing version bafyreia4rb3swb3gkg4siqxvuou2oujcdsdswcw7wxze5wrzytanszwyqe. Show the latest
Query
query · GETParameters
query stringThe request_uri the app received from this host's pushed authorization request endpoint.
Output
application/jsonThe groups the caller may sign in as: the one the app named, or every group on this host where the caller holds a role.
labels
arrayWhat each permission set the app asked for says it is for, in its own words.
loginHint
stringThe group the app named, if it named one.
The scope values the app asked for.
Errors
ExpiredRequest
No description in schema.
#client
object#group
objectProperties
#label
objectSimilar lexicons
semantic matchLexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.
-
fyi.opensocial.approveAuthorization
procedureApprove an app's pending request to sign in as a group. The app gets what the caller's roles in the group allow and nothing more, and every token it obtains is recorded as the caller's. Returns the URL to send the browser back to the app with.
-
fyi.opensocial.getGroupAuth
procedureObtain a DPoP-bound OAuth access token to act as the group DID. The host is the group's PDS and authorization server: the caller authenticates with their personal account (service auth) and presents a DPoP proof; the host issues a short-lived token for the group DID whose space: scopes are exactly what the caller's roles are granted by the space's access record. No group password is involved. The same token may write those kinds of record in the group's public repo too (repoCollections): publish