<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D54z00008SKtr4CADOkta Identity EngineAdvanced Server AccessAnswered2022-12-14T19:03:38.000Z2022-12-04T03:47:22.000Z2022-12-14T19:03:38.000Z
Not able to access non-ASA enrolled server through ASA enrolled bastion

I have a setup where the bastion is enrolled into Okta ASA and am able to access this bastion host using Okta ASA.

 

My usecase is to access a different server (which is not enrolled into Okta ASA and ssh works using username/password) through the above bastion host.

 

When I try that I always get the following error. 

 

The setup is like :    Client -------> GCP Bastion Host (ASA Enrolled) --------> GCP VM (dev-oregon)

 

user@WDTQ7XTJGR ~ % ssh dev-oregon

channel 0: open failed: administratively prohibited: open failed

stdio forwarding failed

kex_exchange_identification: Connection closed by remote host

Connection closed by UNKNOWN port 65535

user@WDTQ7XTJGR ~ %

 

 

My ssh config :

 

Host dev-oregon

 ProxyCommand ssh <Bastion Host> -W %h:%p

 IdentitiesOnly yes

 User dev


  • Mihai N. (Okta, Inc.)

    Hi @User16699974740681484987 (Customer)​ , Thank you for reaching out to the Okta Community!

     

    I ran this scenario by my ASA colleagues and they mentioned that the target server would have to also be enrolled.  

     

    If my answer helped, remember to mark it as best to increase its visibility for other members of the Okta Community who might have the same questions as you. 

     

    Hope my answer helps! 

    --------------------------------

    Community members help others by clicking Upvote or Select as Best on responses. Try it today.

    Expand Post
    Selected as Best
  • Mihai N. (Okta, Inc.)

    Hi @User16699974740681484987 (Customer)​ , Thank you for reaching out to the Okta Community!

     

    I ran this scenario by my ASA colleagues and they mentioned that the target server would have to also be enrolled.  

     

    If my answer helped, remember to mark it as best to increase its visibility for other members of the Okta Community who might have the same questions as you. 

     

    Hope my answer helps! 

    --------------------------------

    Community members help others by clicking Upvote or Select as Best on responses. Try it today.

    Expand Post
    Selected as Best
This question is closed.
Loading
Not able to access non-ASA enrolled server through ASA enrolled bastion