Authorization: Bearer header. Use this for services that expect a freshly signed JWT on every call. You provide the signing method, the key, and the token’s headers and payload; Alumio builds and signs the token for you, filling in the standard typ and alg header values and the issued-at (iat) and expiry (exp) timestamps automatically.
Fields
Sample data
This feature configures a connection rather than transforming data, so there is no before/after to show. A typical HS256 setup looks like this:| Field | Value |
|---|---|
| Encryption Method | HS256 |
| JWT encryption key | your-signing-secret |
| Expire time in seconds | 3600 |
| JWT Headers | {} |
| JWT Payload | { "iss": "your-app", "sub": "service-account" } |