Is there an existing issue for this?
Describe the issue
When creating the User Drive Mapping in AD, the help on the page says by the default mounts will be done in anonymous mode, implicating that the [krb5] prefix needs to be added. However, in the online documentation it says that authentication is done with the Kerberos ticket present, indicating that there is no need to specify [krb5] and that if a the mount is done in anonymous mode - [anonymous] needs to be explicitly added as a prefix.
So I think this is a little misleading. In my environment, the drive mounts automatically on login with the [krb5] prefix. User authentication is needed to access the share and the Kerberos ticket is used accordingly.
Steps to reproduce it
- OS version: Ubuntu 24.04.4 LTS
- Run
adsysctl policy admx all
- Copy the
Ubuntu.adml and Ubuntu.admx files to the AD
- Create an user policy for
User Drive Mapping
Ubuntu users: System information
$ adsysctl version
adsysctl 0.16.3~24.04.2ubuntu0.24.04.1
adsysd 0.16.3~24.04.2ubuntu0.24.04.1
Non Ubuntu users: System information
/
Additional information
/
Double check your logs
Is there an existing issue for this?
Describe the issue
When creating the
User Drive Mappingin AD, the help on the page saysby the default mounts will be done in anonymous mode, implicating that the[krb5]prefix needs to be added. However, in the online documentation it says thatauthentication is done with the Kerberos ticket present, indicating that there is no need to specify[krb5]and that if a the mount is done in anonymous mode -[anonymous]needs to be explicitly added as a prefix.So I think this is a little misleading. In my environment, the drive mounts automatically on login with the
[krb5]prefix. User authentication is needed to access the share and the Kerberos ticket is used accordingly.Steps to reproduce it
adsysctl policy admx allUbuntu.admlandUbuntu.admxfiles to the ADUser Drive MappingUbuntu users: System information
Non Ubuntu users: System information
/
Additional information
/
Double check your logs