![]() short - whether the field should be short or not.Fields with the same position will be added in the alphabetical order. field - prefix of the parameter with field info."Field" parameters with another format or empty value will be ignored. For non trigger-based notifications, it is always set as true.įield_1_short_p:Host - contains data for each field of the attachment. If true all messages will be posted as text of. Use_default_message - false (default) or true. Rc_send_to - #channel or Supports private and public channels and direct messages. Can be useful if the version will be changed. The following parameters can help you customize the alerts: ![]() Rc_user_token - user's API access token created earlier.ģ. Rc_url - the actual URL of your Rocket.Chat instance. The following parameters should be filled: Open the newly added Rocket.Chat media type and replace all with your values. In the Administration > Media types section, import media_rocketchat.yaml.Ģ. If the token is lost or forgotten, you can regenerate or delete the token. The tokens that will be generated are irrecoverable, after generating, you must save it in a safe place. See Rocket.Chat documentation for the information.ģ. Grant to the user a role with create-personal-access-tokens permission. Make sure the user is able to post messages in the required channel.Ģ. Create a user for API or use an existing one. Event updates and resolve messages will be added to the thread of the first message. This guide provides instructions on setting up a media type, a user and an action in Zabbix.īy default, all new alerts will be posted as messages with an attachment card. ![]() You cannot login with joe by your ldap password nor by your local password any more.This guide describes how to integrate Zabbix 6.2 installation with Rocket.Chat using the Zabbix webhook feature. For example if you created a local user with username joe, then enable ldap and try to login with username joe (who exists on your ldap server), it will silently fail without any error message in your log simply saying username or password do not match. If you cannot login without getting any error messages (the last thing in log you see is Attempt to bind ), make sure the username of your ldap account does not match any username of a local account. ![]() Troubleshooting I cannot login even everything looks good We’re not experts on LDAP, so there might be lots of features we don’t know about and we’d love to have your comments and feedback of what we can do to improve it. To enable Stunnel automatic startup change the ENABLED variable in /etc/default/stunnel4 to 1: # Change to one to enable stunnel automatic startupįinally on the Rocket.Chat server under /admin/LDAP set Create a new configuration file /etc/stunnel/nf with following content: options = NO_SSLv2 Use stunnel to create a secure connection to the LDAP server. When you enable LDAP the login form will login users via LDAP instead the internal account system. Proxy User password = urpass (Proxy Users passwordįor now (until we add more input fields to LDAP) set it like this: (This is based on the above assumptions, replace with your environment) Logon with username:.Proxy User = or CN=rocket service,CN=Users,DC=domain,DC=com (DN or userPrincipalName).Group = CN=ROCKET_ACCESS,CN=Users,DC=domain,DC=com (Access Control Group).To configure LDAP authentication, go to /admin/LDAP, enable LDAP and add configurations to connect with your LDAP server.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |