Hi thuy.hoang In the API explorer section, you have to select "<> LdapAttributeMap" andchoose the GET button. Then you have to choose the "TRY IT OUT!" button. You'll have the response body: At the end of the script you'll find the informations you a...

Hi thuy.hoang. This is my Json commands for LDAP attribute mapping: { "version": "dpynuucqo55jf", "name": "department", "ldapAttributeMaps": [ { "ldapName": "memberOf", "ciscoName": "GROUP_POLICY", "...

Thank you, rfranzke,Your contribution is appreciated by me.I resolved the problem too, in a way similar ti yoursI used one tunnel-group too, but in my solution the client continues show me the tunnel group options but now is not a problem.My problems...

Thank You Marvin fr your answer. I deleted the aliases in the connection attribute but the result is the same. In old ASA, to obtain the result, I had to unchecked the  "Allow user to select connection profile on the login page" on connection profile...

Hi  rfranzke.I have the same problem. I was able to use API to configure attribute map and the associatione with the realm server. If I watch the running config all seems OK, but when the VPN user try to connect, he can choice the tunnel group and if...