MQ is supported on the nais platform on-premises and on GCP. We recommend using kafka where possible and sensible.
When ordering groups for existing service users the password will be reset. If you do not want the password to be reset, contact windows admin and ask them to add the existing user to the AD group and set the "extensionAttribute9" property on the user
Access to basta (and fasit) can be obtained by requesting access from identity management.
Access to development environments (including legacy u, t and q environments):
0000-GA-env-config-TestAdmin - Fasit T/Q
Access to production environments (including legacy p environment):
0000-GA-env-config-ProdAdmin - Fasit P
Order the group by using your applications name, the group name in AD will be 0000-GA-MQ- followed by the application name. If no service account exists with the name srv + application name, it will be created and added to the group. If the user already exists the user will be added to the group and the password will be updated and uploaded to vault in the serviceuser directory.
From vault you can then mount this secret into your pod to authenticate with MQ.
These servers are available from on-premises and GCP alike.
The application needs to implement MQ authentication using the client libraries, as opposed to previously just sending username.
If you are using MQ client lower than 18.104.22.168 set this parameter when connecting:
Setting this in java: