This introduces a user info endpoint as noted in #105. The endpoint is entirely optional, is specified by the property in metadata as per the Metadata spec, and the return is as already identified in the profile parameter. The request is a GET request with the appropriately scoped token in the Authorization header. The listed purpose of the endpoint is to retrieve or refresh profile information without going through the entire flow.
This also clarifies the profile return, specifically name property concern mentioned in #93, specifying that as the entire profile is non-authoritative, and represents what the user wishes to share with the client, intent should be considered to be a display name.
This introduces a user info endpoint as noted in #105. The endpoint is entirely optional, is specified by the property in metadata as per the Metadata spec, and the return is as already identified in the profile parameter. The request is a GET request with the appropriately scoped token in the Authorization header. The listed purpose of the endpoint is to retrieve or refresh profile information without going through the entire flow.
This also clarifies the profile return, specifically name property concern mentioned in #93, specifying that as the entire profile is non-authoritative, and represents what the user wishes to share with the client, intent should be considered to be a display name.