Account Mapping

The middleware maintains a database that links external user accounts with robot - internal cluster accounts.
This database ensures a secure and efficient mapping process, allowing users to interact with the HPC system through the middleware.

External User Account

Users are provided with external user accounts, which they use to access the middleware.
These users do not have direct access to the HPC infrastructure; instead, they interface with the middleware to submit jobs and manage tasks.
Authentication is handled by the middleware, ensuring that users can only utilize middleware functions and not directly interact with the HPC resources.

Robot Account - Internal Cluster Account

For each job submitted by an external user, the middleware assigns an robot - internal cluster account from a pre-defined pool of accounts.
The robot cluster account is responsible for executing the job on the HPC system.
These robot accounts are managed in such a way that they remain within the HPC infrastructure, ensuring that they are not exposed or accessible outside the cluster environment.

Summary

In summary, the middleware serves as a bridge between external user accounts and robot cluster accounts. External users authenticate through the middleware, which in turn assigns an robot cluster account for each job. This robot account is then used to perform the actual job execution within the HPC infrastructure, maintaining security and efficiency.