Implementing what is described in Google's OAuth 2.0 for Server to Server Applications, Forming the JWT claim set.
get_auth_bearer is only public method, will handle generating and refreshing token.
Depends on D12753
Details
Details
Call get_jwt_token and test if returns the correct JWT token in the format
{Base64url encoded header}.{Base64url encoded claim set}Later in the stack this token is used to make an HTTP call to get an access token for the FCM push service.
Diff Detail
Diff Detail
- Repository
- rCOMM Comm
- Branch
- land-fcm
- Lint
No Lint Coverage - Unit
No Test Coverage
Event Timeline
| services/tunnelbroker/src/notifs/fcm/mod.rs | ||
|---|---|---|
| 20 ↗ | (On Diff #42296) | Docs say: Token must be a short-lived token (60 minutes) and in a reasonable timeframe. so I set this to 55 minutes to leave a buffer to refresh but keep it as long as possible to avoid refreshing this too often. |
| services/tunnelbroker/src/notifs/fcm/token.rs | ||
| 21 ↗ | (On Diff #42296) | This is optional to allow creating instances of this without calling OAuth, I want to create FCMToken and FCMClient regardless of minting access token |
| 36–40 ↗ | (On Diff #42296) | generating this when is None in next diff |
| 57 ↗ | (On Diff #42296) | Link to why this scope: https://firebase.google.com/docs/reference/fcm/rest/v1/projects.messages/send |
| 62–65 ↗ | (On Diff #42296) | See Computing the signature here |