Credentials: what changed from OpCon Classic
This page maps OpCon Classic concepts to their OpCon Continuum equivalents. It is a conceptual mapping under review, and it deliberately does not compare the two products' platform or job-type breadth. Use it to translate what you already know — not as the basis for a migration plan. Confirm specifics with your Continuous contact.
What this solves
In OpCon Classic, a job ran under a Batch User and each job type carried its own credential configuration. In OpCon Continuum, credentials live in a Connection (created once, stored centrally, and delivered to the agent only at run time), while where a job runs is decided by agent assignment. If you carry over the "credentials on the job" habit, you'll miss the safer model.
What you get. The mapping from Batch Users to Connections, and how to set a job up so no secret ever lives in the workflow.
Related topics
- Manage connections (Administrator)
- Set up database connections (Administrator)
- Where jobs run: what changed from OpCon Classic