You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Introduction

Like the RED Client, Azkaban Executor Servers create and use an in-memory Profile at runtime for access to the required runtime credentials for the Metadata, Sources and Target connections. Since an Azkaban job can be run on any Executor on any machine we store any required credentials (passwords encrypted) and connection strings in a central location under the "redamin"."ws_scheduler_profile" table of the RED metadata repository database.

The Azkaban Executor Servers retrieve credentials and connection strings from the "redamin"."ws_scheduler_profile" at job runtime and merges any connections missing from the profile records with those found in the RED metadata. This merging process allows for Windows style authentication to work without the need to maintain the Scheduler Profile.

Azkaban Security and Profiles

Scheduler Profile Record Structure

The structure of the profile records in "redamin"."ws_scheduler_profile" is like so:

RED Connection Name (lowercased)ODBC Connection StringUser NameWhereScape Encrypted Password
repositorydsn=$DSN$;uid=$USER$;pwd=$PASSWORD$;redscheduler_userVTj0Q2xapJEWpQed8DJYvBEEnRedR94NstiHJUlLt0gC


Maintaining the Scheduler Profile 





  • No labels