mirror of
https://github.com/hanzoai/team.git
synced 2026-09-30 01:57:35 +00:00
6a87848c45
* [MM-70140] Remove experimental AD/LDAP login button color settings Remove the dead-code LdapSettings.LoginButtonColor / LoginButtonBorderColor / LoginButtonTextColor experimental settings. These values were plumbed into the client config but never consumed by the web or mobile clients, so no AD/LDAP login button was ever rendered or colored. Removes the fields from the server config struct and defaults, the client config payload, the Admin Console Experimental Features section, the webapp config type, related en.json strings, API definitions, docs, and test/default config fixtures. Co-authored-by: mattermost-code <[email protected]> * [MM-70140] Add test guarding removal of LDAP login button color keys Assert that GenerateLimitedClientConfig still emits LdapLoginFieldName under an LDAP license but never emits the removed LdapLoginButtonColor/BorderColor/ TextColor keys, guarding against reintroduction of the dead settings. Co-authored-by: mattermost-code <[email protected]> * [MM-70140] Remove LDAP login button colors from webapp LdapSettings type Keep AdminConfig LdapSettings in sync with the server model after the experimental AD/LDAP login button color settings were removed. Co-authored-by: mattermost-code <[email protected]> * [MM-70140] Update admin console index test after LDAP color removal Drop experimental/features from the ldap search expectation now that the AD/LDAP login button color settings are no longer under Experimental. Co-authored-by: mattermost-code <[email protected]> * Address PR feedback: remove test for removed LDAP login button color settings Per @lieut-data's review, drop TestGenerateLimitedClientConfigOmitsLdapLoginButtonColors; there's no need to perpetually test that a removed feature stays removed. * chore: retrigger CI after GitHub Actions service outage Co-authored-by: mattermost-code <[email protected]> * chore: retrigger CI after Actions service recovery Co-authored-by: mattermost-code <[email protected]> --------- Co-authored-by: mattermost-code <[email protected]> Co-authored-by: mattermost-build <[email protected]> Co-authored-by: Hanzo Dev <[email protected]>
Keycloak development environment
Setting up
OpenID
Overwrite your OpenIdSettings section in your config.json file by running make config-openid and restarting your server.
SAML
Overwrite your SamlSettings section in your config.json file by running make config-saml and restarting your server.
LDAP
Overwrite your LdapSettings section in your config.json file by running make config-ldap and restarting your server.
Credentials to log in
-
Admin account, used to log in to the Keycloak Admin UI:
admin/admin
-
User accounts, used to log in to Mattermost:
homer/passwordmarge/passwordlisa/password
Updating the realm-export.json
The realm-export.json file is automatically imported by the keycloak development container. If you make any modifications to this file or to the base configuration, export it by running a terminal in the container and running:
/opt/keycloak/bin/kc.sh export --realm mattermost --users realm_file --file /opt/keycloak/data/import/realm-export.json