Pablo,
So I am not sure I totally get your use case or exactly what you are looking for but I suspect you should create a communities idea for it.
I am guessing here,
But I suspect you have a
client -SSH-> Gateway (correct?)
And that policy I assume does a require SSH credentials. (the ssh key from the gateway will be the gateways sshkey)
Then you are doing an authorize of this or a lookup in your ldap?
Is it an LDAP attribute you are trying to get?
Or something with the above handshake?
Then I assume you are routing via SSH to your backend.
GW -RouteViaSSH-> Backend
Which would present its ssh key. There is a checkbox option in the route to verify a key but it has to be loaded not in a variable format.
Both the require SSH and route SSH dont have any variables associated with the view info so there are no variables out of these calls. We might be able to audit some raw.tcp but I am trying to understand what key you are trying to get from where first so I know if I might have missed something. But it will likely require a communities idea.
Thanks.