Great, good to hear. Just as an aside, the import feature can be toggled on/off with a command line parameter, by the way. See
https://docs.openvpn.net/under-the-hood/vpn-client-basic/ to learn how.
Also, every user account has its own unique set of certificates and you can't mix up credentials and certificates. A set of certificates imported from a server for user A won't work with credentials for user B, for example. The server-locked profile is the solution to that; it just contains information to confirm the identity of the server and to negotiate with the server for a connection profile that contains certificate for the specific user you're logging on as at that moment, and once the connection is dropped, that temporary connection profile is deleted from the client. The client is then again ready to accept a connection for another user, any user, on that Access Server, provided you specify the correct credentials.
It is possible to completely ditch certificates but this lowers security rather a lot - don't do that.
If user a works on machine x all the time, then what you've just tested and used is perfectly fine. If you expect machine x to be used by users a, b, c, d, and e, then you can either import profiles for each one, or use a server-locked profile instead. When you download the connect client from the access server's web interface while logged on as a standard user that has no autologin privileges, it will automatically come pre-loaded with a server-locked profile.
