Administering Cloud EPM: The Platform Beneath the Business Processes · Module 11 · Automation
Authentication and credential handling
Lesson 124 of 201 · 14 min
Sign in interactively, create an encrypted credential file, sign in using it, show the file permissions applied and why, show OAuth token-based authentication as the alternative, and show authentication in an SSO-enabled environment. NEVER PUT A PLAIN-TEXT PASSWORD IN A SCRIPT. The encrypted credential mechanism exists precisely for this and it takes two minutes. The credential file's permissions matter. Understand what protection is applied, and confirm the server's own access controls are consistent with it. IN AN SSO-ENABLED ESTATE, THE ACCOUNT RUNNING AUTOMATION AUTHENTICATES THROUGH THE TRADITIONAL ROUTE, not the federated one. That is Module 8's administrator route — and it is why you do not remove it. Token-based authentication is the stronger option where it fits.
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Administering Cloud EPM: The Platform Beneath the Business Processes, with a certificate on completion and a fourteen-day refund window.
In this module: Module 11 · Automation
- 1Three tools, one questionFree preview
- 2Job Scheduler
- 3Installing and configuring the automation utility
- 4Authentication and credential handling
- 5The command surface
- 6Scripting patterns: backup and export
- 7Scripting patterns: data load and refresh
- 8Error handling and logging
- 9Scheduling and service accounts
- 10REST APIs and when to reach for them
- 11The integration agent
- 12What breaks
- 13Lab: automate it, and write the runbook
