Configure the Service Bus for Mobile

Creating a Service Bus and Queue in the Azure Portal

When a Service Bus Queue needs to be created, refer to the latest instructions as outlined by Microsoft in Quickstart: Use Azure portal to create a Service Bus queue.

If you already have an existing Service Bus in Azure, you are welcome to use the existing setup. You just need to create a new queue within your existing Service Bus to be used by the Mobile App.

The following steps explain what is required for the Mobile App integration:

  1. In the Azure Service Bus portal go to the Shared access policies page.

  2. Find the policy called RootManageSharedAccessKey. If you don't have one yet, create one by that name and select the Manage option and save it.

  3. On the RootManageSharedAccessKey policy you can see the Primary Key field. Make note of where this is. We have to use it in a step down below.

  4. Next, navigate to the Queues page and create a new queue.

  5. Create a new Shared Access policy names RootManageSharedAccessKey for the new queue.

    alt

  6. Do not check any of the options, using the defaults is fine. Take note of the name of the newly created queue.

Next you will need to follow the instructions below to create a credential for the Service Bus and add the Service Bus as a foreign system in Privilege Manager.

Adding the Service Bus as a Foreign System

The Azure Service Bus requires a Foreign Systems configuration in Privilege Manager. To configure a Service Bus instance with a custom URL and credentials follow these steps:

  1. In the Delinea Privilege Manager Console, click Admin | Configuration.

  2. Click the Credentials tab.

  3. Click Create.

    • Enter a Name, for example Azure Service Bus Credential.
    • Set the Account name to RootManageSharedAccessKey.
    • Set the Password to the value of the Primary Key obtained during the Azure Service Bus configuration procedure step 3 under "Creating a Service Bus and Queue in the Azure Portal" above.

  4. Click Save Changes.

    sb credential

  5. Navigate to Admin | Configuration and select the Foreign Systems tab.

  6. Click the Azure Service Bus option.

  7. Click Create at the prompt box for creating a new service bus.

    new foreign system

    • Enter a Name, for example Mobile App Azure Service Bus.
    • Set the ServiceBus Name to the namespace of the Service Bus from the Azure Portal. To find this value, open the Azure Portal, locate the Service Bus that is being used for this integration (refer to the intro above). Go to the Properties page and locate the Name property (generally, this is the same name as the instance you just located in the list of Service Bus instances).
    • Set the Enabled switch to No for now.

  8. Click Create.

  9. Enter the requested information at the Mobile App Azure Service Bus configuration page.

    • Set the credential to the credential created in step 3 of this procedure (Azure Service Bus Credential).
    • Leave the URL field as is (and ignore the fact that it's called URL – it's just the Service Bus name).
    • Make sure the URI matches the first part of the namespace created in Azure.
    • Set the QueueName to the same queue name created above in step 4 under "Creating a Service Bus and Queue in the Azure Portal".
    • Set the Queue Policy Name to RootManageSharedAccessKey.
    • Set the Queue Policy Secret to the Primary Key as obtained in step 5 under "Creating a Service Bus and Queue in the Azure Portal" above.

  10. Click Save Changes.

    config

  11. Enable the Service Bus and toggle Enabled to Yes.

  12. To verify everything is working correctly, open your browser and point it to the ServiceBus worker service:

    • On-Premises: https://yourinstance.privilegemanager.com/Tms/ServiceBus/WorkerService.svc
    • Cloud: https://yourinstance.privilegemanagercloud.com/Tms/ServiceBus/WorkerService.svc

    Wait for the page to respond. See example below. You are now ready to install the Delinea ACS application on your mobile devices.


If the page does not respond, try the URL again in a few minutes. If the error persists, perform the recommended [Troubleshooting](troubleshooting-bus.md).

alt