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
Once a user AS is configured, we obtain a host id and secret that will be valid for the existence of this AS, as well as a VPN client certificate.
It maybe useful to be able to invalidate them for some reasons:
The credentials are used somewhere else, and we want to invalidate other "usages" but this.
The credentials were compromised.
This by itself is not enough to avoid the user AS to connect to the AP.
Ideally we would be able to prevent existing user ASes configured before selecting "Invalidate Previous Credentials" from even connecting to the AP.
The text was updated successfully, but these errors were encountered:
Once a user AS is configured, we obtain a host id and secret that will be valid for the existence of this AS, as well as a VPN client certificate.
It maybe useful to be able to invalidate them for some reasons:
This by itself is not enough to avoid the user AS to connect to the AP.
Ideally we would be able to prevent existing user ASes configured before selecting "Invalidate Previous Credentials" from even connecting to the AP.
The text was updated successfully, but these errors were encountered: