scottsignal opened a new issue, #10030:
URL: https://github.com/apache/cloudstack/issues/10030
<!--
Verify first that your issue/request is not already reported on GitHub.
Also test if the latest release and main branch are affected too.
Always add information AFTER of these HTML comments, but no need to delete
the comments.
-->
##### ISSUE TYPE
<!-- Pick one below and delete the rest -->
* Enhancement Request
##### COMPONENT NAME
<!--
Categorize the issue, e.g. API, VR, VPN, UI, etc.
-->
~~~
API/UI
~~~
##### CLOUDSTACK VERSION
<!--
New line separated list of affected versions, commit ID for issues on main
branch.
-->
~~~
4.19.1.3
~~~
##### CONFIGURATION
<!--
Information about the configuration if relevant, e.g. basic network,
advanced networking, etc. N/A otherwise
-->
LDAP w/Active Directory
##### OS / ENVIRONMENT
<!--
Information about the environment if relevant, N/A otherwise
-->
Ubuntu 22.04
##### SUMMARY
<!-- Explain the problem/feature briefly -->
This is a request for some general enhancements when linking LDAP Accounts
via linkaccounttoldap
1. The GUI does not show that an account in LDAP linked at all. it would be
nice to have some sort of indicator.
2. When an Account is linked to LDAP via linkaccounttoldap, you should not
be able to create manual users in this account in the API or GUI. If an
account is linked to LDAP, it should enforce ldap auth.
3. There is no way to fix a DN should you need to update the value without
editing the database.
##### STEPS TO REPRODUCE
<!--
For bugs, show exactly how to reproduce the problem, using a minimal
test-case. Use Screenshots if accurate.
For new features, show how the feature would be used.
-->
1. Just show on the account Details if the account is LDAP linked or not.
2. Don't allow new users to be created in the account after it is linked to
LDAP via linkaccounttoldap.
3. Ability to update ldapdomain value on an account should it need to change
<!-- Paste example playbooks or commands between quotes below -->
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
