You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Allow the client to include multiple alias hostnames in its enrollment request, where the additional hostnames are added as aliases in known_hosts output. This will be useful for multi-homed clients. The aliases should be validated against the client SSL cert.
The text was updated successfully, but these errors were encountered:
@christodenny The body could be changed to JSON and the client's pub key and aliases marshaled. Otherwise I'd say a header tag sounds cleaner than using the URL.
I would tend to prefer just putting them in the URL, but headers or JSON could be fine too.
If I have a spare moment, I might get to this task this week or the next.
We're going to add a server-side configuration too, where a hardcoded mapping of hosts => aliases can be added (we have a small-ish number of ones that aren't on TLS certs, so that's the easiest bodge for us)
For passing aliases via the URL, do you imagine that we'd join the list of aliases on a given separator? Then pass the joined list as a single variable in the URL, or is there a more clever way todo this?
Allow the client to include multiple alias hostnames in its enrollment request, where the additional hostnames are added as aliases in known_hosts output. This will be useful for multi-homed clients. The aliases should be validated against the client SSL cert.
The text was updated successfully, but these errors were encountered: