Confirm
192
edits
Changes
→3. Applications permissions
The following steps occur in this flow:
# User clicks Authorize# Authorize button posts to the Mozilla Presence authorization page
# User acknowledges the AppService they're granting and allows it
# User is redirected back to the AppService
==== Technical Details ====
The page URL the Authorize buttons posts to is : https://<node>.presence.mozilla.com/<appid>/grant?redirect=<url>&id=<userstring>where Where <node> and <appid> are values known by the registered application, <url> is theurl to redirect back to, and <userstring> is the user-meaningful string indicating that shouldusually be their login name (or something short and meaningful to distinguish multiple identities on a single AppService if applicable).
In the example above, the user Marge happens to be logged into BeerChat as 'Fred', so this identifier is attached during authorization so that when Marge manages her Presence she can see that she appears online as Fred to BeerChat.
