pa3yq (pa3yq) asked a question.
What is the best practice for using an ASA Service User with GitHub Actions
I code that I would like to deploy to an ASA secured server using GitHub Actions.
I'd like to use a push model of deployment so I'd need some way for the GitHub Action to invoke behavior on the server. What is the best practice for setting up a user that a GitHub action could use to run commands over SSH? I've looked at https://help.okta.com/asa/en-us/Content/Topics/Adv_Server_Access/docs/services.htm but it seems like it's geared towards long running CI/CD servers, not the fresh environments you get with GitHub Actions.
Hello @pa3yq (pa3yq) Thank you for reacting out to our Community!
Please see blow documentations that should provide the information you are looking for:
https://github.com/fortyfivan/okta-asa-aws-quickstart
https://github.com/aws-quickstart/quickstart-okta-asa
Community members help others by clicking Like or Select as Best on responses. Try it today.
Watch and Learn: New Okta how-to videos, plus what's new this month in the May newsletter.
Thank you, can you point me to any one of the particular files that allows for silent logging in on a client machine that's ephemeral?
Or how to deploy a service user to an ephemeral server?
@pa3yq (pa3yq) Have you reviewed this article?
https://aws-quickstart.github.io/quickstart-okta-asa/
I did but I am failing to understand how it's related to my original question.
At this time this is all the information I was able to find on this setup, if you need additional assistance I would recommend to open a case with Support.