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
{{ message }}
This repository has been archived by the owner on Jan 10, 2023. It is now read-only.
Are LDAP configurations something that can be handled by Chef? I'm having troubles determining how those are persisted. Is that information in the database, or in a configuration file located on the server?
The text was updated successfully, but these errors were encountered:
I'm fairly confident that its stored in the database. How deep are you looking to manage the configuration? Just the server/attribute properties or users/permissions as well? Let me poke around the database to see how difficult either would be.
mysql> use stash;
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A
Database changed
mysql> select * from app_property;
+---------------+----------------------------------------------+
| prop_key | prop_value |
+---------------+----------------------------------------------+
| instance.home | /var/atlassian/application-data/stash/shared |
| instance.name | Stash |
| server.id | XXXX-XXXX-XXXX-XXXX |
+---------------+----------------------------------------------+
3 rows in set (0.00 sec)
Are LDAP configurations something that can be handled by Chef? I'm having troubles determining how those are persisted. Is that information in the database, or in a configuration file located on the server?
The text was updated successfully, but these errors were encountered: