Oracle Integration Cloud: Building Integrations That Survive Production · Module 12 · Security: credentials, certificates and network
OAuth, and which grant to use
Lesson 120 of 175 · 3 min
Client credentials, resource owner, and the refresh that expires while you are asleep. Choosing per system rather than per habit. CLIENT CREDENTIALS IS THE GRANT FOR AN INTEGRATION AND IS RIGHT ALMOST ALWAYS. The integration IS the client; it authenticates as itself, with no user involved, and there is nobody whose consent is being represented. That is exactly the shape of an unattended process, and it is why this grant exists. RESOURCE OWNER PASSWORD is a user's username and password held by the integration. It is available on many systems and it is a compromise: the integration now holds a person's credential, so it can do everything that person can do, and everything it does is attributed to them. It is defensible only when a system offers nothing better, and then the account should be a dedicated service user rather than a real person's. AUTHORIZATION CODE has no place in…
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Oracle Integration Cloud: Building Integrations That Survive Production, with a certificate on completion and a fourteen-day refund window.
In this module: Module 12 · Security: credentials, certificates and network
- 1What an integration actually holds
- 2Where credentials liveFree preview
- 3The service account and least privilege
- 4OAuth, and which grant to use
- 5Certificates: trust, identity and expiry
- 6Rotation without an outage
- 7Network: allowlists and private endpoints
- 8What ends up in a log
- 9What breaks: four security failures
- 10Lab briefing · Audit an integration for exposure