Within Rundeck, is it possible to restrict the ip source/locations for an api key to be used? For instance, the “admin” userid’s api key can only be used by scripts/calls from the Rundeck server itself. Any suggestions on how to restrict the source calling location of specific api keys (as normal regular end-users’ api keys can be from their laptops and such)?
Question
Restricing Admin API Access
Hi Russ, Rundeck does not natively support IP restrictions on a per-API-key basis. The API token system functions strictly as a token-to-username mapping with no source IP binding. A solid approach would be to enforce these restrictions using a load balancer (LB) or reverse proxy in front of Rundeck or by configuring firewall rules.
Login to PagerDuty Commons
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.