I would appreciate some help or guidance in this.
1.The private key required for signing the JWT will be securely stored in Azure Key Vault.
2. Generate JWT Token (Compose/Custom Action):
Build the JWT Header (JSON → Base64URL encode).
Build the JWT Payload with iss, prn, sub, iat, exp (JSON → Base64URL encode).
Sign the concatenated string with the private key using RS256 → produce the Signature.
Final token: base64url(header).base64url(payload).base64url(signature).
3.Use an HTTP action in Power Automate to call required endpoint:
Method: GET / POST (as required by the Oracle endpoint)
URL: https://<oracle-host>/path/to/api/endpoint
Headers:
Authorization: Bearer <JWT_TOKEN>
Content-Type: application/json
Could you please review the above approach and confirm if this aligns with the recommended pattern? Additionally, I would appreciate any suggestions, best practices, or considerations—especially regarding JWT generation within Power Automate or integration with Azure Key Vault—that we should incorporate.
Thank you

Report
All responses (
Answers (