Skip to content


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

MQ groups and users are ordered using basta. For legacy applications registered in fasit use "AD groups" on the "Create" tab, for all other applications use "Custom AD groups".

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.



QueueManager Hostname Port
MQLS01 b27apvl219.preprod.local 1413
MQLS02 b27apvl220.preprod.local 1413
MQLS03 b27apvl221.preprod.local 1413
MQLS04 b27apvl222.preprod.local 1413


QueueManager Hostname Port
MPLS01 1414
MPLS02 1414
MPLS03 1414
MPLS04 1414

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 set this parameter when connecting:


Setting this in java:

connectionFactory.setBooleanProperty(JmsConstants.USER_AUTHENTICATION_MQCSP, true);