Single Sign On Configuration

The guide below details how to setup a single sign-on integration in the LogiSense Billing application. Both Azure AD and Okta integrations are covered in this guide.

Okta Configuration Process

Setup a new Application in the Okta Admin Portal

The fist step is to create an application in the Okta portal for the LogiSense Billing integration.

1. On the left hand side click on Applications to show the sub menus

   

2. On the Applications sub menu click Create App Integration

   

3. On the Create New App Integration pop-up select SAML 2.0 and click Next
   

   

4. On the Create SAML Integration page enter an application name (for instance, LogiSense Billing) and click Next

   

5. Enter the Single sign-on URL. This will be the URL used to access your LogiSense Billing instance plus the path to the AuthorizationServer ( /AuthorizationServer/Saml2/ACS )
   

   

6. Enter the Audience URI (this will be the same domain name as above, but without the AuthorizationServer… details)

   

7. All other settings can be left as default, at the bottom of the page click Next

8. On the following page select I'm an Okta customer adding an internal app option and then the This is an internal app that we have created option and click Finish

Capture SAML Certificate Details in Okta

Next certain details are required from the Okta application data in order to configure SAML settings in the LogiSense Billing application. You can copy these details into notepad or any text editor.

1. On the application page that loads scroll down to the SAML Signing Certificates section

2. Next to the SHA-2 cert click on Actions and then View IdP metadata

3. On the metadata page that loads copy the URL of that page (e.g. https://dev-xxxxxxxx.okta.com/app/exkaffbk7gT0TrGxi8d7/sso/saml/metadata) and copy the value within that page on the very first line called entityID

Configure the SAML Settings in LogiSense Billing

1. Login to LogiSense Billing

2. Load the Setup / Users & Accounts / Owners screen

3. Under Owner Configuration click on SAML Setting

4. Click Enabled if it is not already selected

5. In the Entity ID field paste in the entity id from the metadata (just the URL without quotes)

6. In the Provider Metadata URL field paste in the metadata URL you previously copied

7. Click the Get Token button and a token will be generated

8. Copy the SCIM Access Token that is generated (this will be needed as part of the SCIM Configuration below)

9. Click Save to save the SAML settings

Configure SCIM to Manage Users in Okta

1. Access the Okta admin portal

2. Access the Application you setup for the LogiSense Billing integration

3. Click on the General link

4. Under the App Settings section click Edit

5. Check the option Enable SCIM provisioning

6. Click Save

7. Once the change is saved a new Provisioning link will appear under the application where SCIM settings can be populated
   

   

8. Click on Provisioning

9. On the Provisioning Settings page click Edit

10. In the SCIM connector base URL field enter the domain of your LogiSense Billing system followed by /ResourceServer/api/SCIM
    

    

11. In the Unique identifier field for users field enter your Okta supplied identifier

12. In the Supported provisioning actions section enable Push New Users, Push Profile Updates and Push Groups

13. Change the Authentication Mode to HTTP Header authentication

14. Under the HTTP Header section in the Bearer field paste the SCIM Access Token you copied earlier from the SAML Settings in the LogiSense Billing application

15. Click Test Connector Configuration

16. On the pop-up that appears the test should show that the testing of the create, update and push functions worked

    

17. Close the Test Connector Configuration pop-up and Click Save

18. Next, we need to grant Okta user management permissions in LogiSense Billing. On the Provisioning page click the Edit link

19. Next to Create Users click Enable

20. Next to Deactivate Users click Enable

    

21. Click Save

Configure a SCIM Role Group in LogiSense Billing (Optional)

When Okta groups are pushed to LogiSense Billing they will be created as SCIM Role Groups. The permissions that the newly created SCIM Role group have by default will depend on what role group in LogiSense Billing is configured as the ‘SCIM Default’ role group.

By default the SCIM Default role group set in LogiSense Billing is the ‘ReadOnly’ role group (shown in the image above). This is a core role group that grants the user read only access to all menus and screens but no rights to modify anything.

To define different default role group permissions for the role groups created when groups are pushed from Okta you can simply create a new role group in LogiSense Billing with the desired permissions and enable the ‘SCIM Default’ setting on the new group. For instance, you may wish the default permissions for groups pushed from Okta to be limited to read-only access to the home and account menus only.

After the Okta groups are pushed to LogiSense Billing and the SCIM Role groups are automatically created you can then access LogiSense Billing and modify the particular SCIM Role Group’s permissions as needed (i.e. grant additional permissions beyond what the SCIM Default role group has provided).

Configure Application Permissions in Okta

The steps below will assign Okta people and push groups to the Okta Application (i.e. LogiSense Billing). People assigned to the Application in Okta will be created as users in LogiSense Billing. Groups pushed from the Okta Application will define the permissions that the users under that group will have in the LogiSense Billing application (i.e. pushing groups in Okta will create role groups in LogiSense Billing).

Assigning People / Creating LogiSense Users From Okta

1. On the Application page click on Assignments

2. On the Assignments page click the Assign button

3. You will be presented with two options, Assign to People and Assign to Groups. Select Assign People

4. Click Assign next to the person
   

   

5. On the Assign pop-up that appears leave the values as is and select Save and Go Back

6. Assign additional people as needed, when finished click the Done button

7. The users you added should be listed in LogiSense Billing
   

   

8. You can verify that the user/group was created in LogiSense Billing on the Setup / Users & Accounts / Users screen and Role Groups screen

   

If the person in Okta has no group set on it then the user will be created using the ReadOnly role group. To grant a user additional permissions they will need to first be assigned to a group in Okta and then their group must be pushed to LogiSense Billing. See the steps below for instructions.

Pushing Groups in Okta / Creating LogiSense Role Groups

1. On the LogiSense Application page in the Okta Portal click on Push Groups

2. Click the Push Groups button and then select an option to find a group
   

   

3. After an Okta group has been selected click Save

4. The Role Group will now be created in LogiSense Billing
   

   

5. In the Okta portal if you assign people setup under the LogiSense Application to a group that has been pushed to LogiSense Billing then the corresponding user’s role in LogiSense Billing will be updated to show a SCIM role (i.e. the user will have the permissions setup for the role groups that are attached to that role)
   

   
   

   

6. Repeat the steps above to push more groups to LogiSense Billing.
   Note: the auto-generated ‘Name’ values as shown in the image above can be changed to something more user friendly (i.e. Sales, Accounting, Support, etc.)

7. You can now configure the permissions for the role groups that you have pushed to LogiSense Billing in order to define what Okta users in those groups can do in LogiSense Billing
   

   

Login to Test SSO Integration

1. Log out of LogiSense Billing

   

2. On the Login page a new Log in with SSO option will be available

   

3. Click on Log in with SSO

4. You will be redirected to the Okta login page

   

5. Enter your Okta username and password and click Sign In

6. After entering valid login Okta credentials you will be directed to the LogiSense Billing application and logged in

The signed in user will now be able to view/modify all of the screens in LogiSense Billing that their role group configuration permits them to access.

Azure Configuration Process

Setup a new Application in the Azure Admin Portal

1. Log into the Azure Portal and click on Enterprise Applications

   

2. Click on New application

   

3. Click on Create your own application

   

4. Give the new Application a Name and then select Integrate any other application you don’t find in the gallery and click Create (Note: application creation may take some time)

   

5. Once the application is created, click on Set up single sign on

   

6. Select SAML

   

7. Under the Basic SAML Configuration section click Edit on the right

   

8. Enter the Entity ID (this is the URL used to access your LogiSense Billing instance)

9. Enter the Reply URL (this is the URL used to access your LogiSense Billing instance with the path to the AuthorizationServer appended ( e.g. https://acmebillingportal.com/AuthorizationServer/Saml2/ACS ). Note: the auth server path is case sensitive (e.g. must be Saml2, not saml2)
   

   

10. Click Save

11. Once saving is complete click the X to close the Basic SAML Configuration

12. Next to set up a test user to have access to the application - click Users and Groups on the left sidebar

    

13. Click Add user/group

    

14. Add your Azure account to the application, and click Assign

15. Return to the Single sign on page

    

16. Under the SAML Certificates section copy the App Federation Metadata Url and paste it somewhere you can easily access it again (e.g. notepad or any text editor)

    

17. Under the Set up <application name> section copy the Azure AD Identifier and paste it somewhere you can easily access it again (e.g. notepad or any text editor)

    

Configure the SAML Settings in LogiSense Billing

1. Login to LogiSense Billing

2. Load the Setup / Users & Accounts / Owners screen

3. Under Owner Configuration click on SAML Setting

4. Click Enabled if it is not already selected

5. In the Entity ID field paste in the Azure AD Identifier you copied during the Application setup process

6. In the Provider Metadata URL field paste in the Azure APP Federation ID you copied during the Application setup process

7. Click the Get Token button and a token will be generated

8. Copy the SCIM Access Token that is generated (this will be needed as part of the SCIM Configuration below)

9. Click Save to save the SAML settings

Configure a SCIM Role Group in LogiSense Billing (Optional)

When Azure groups are pushed to LogiSense Billing they will be created as SCIM Role Groups. The permissions that the newly created SCIM Role group have by default will depend on what role group in LogiSense Billing is configured as the ‘SCIM Default’ role group.

By default the SCIM Default role group set in LogiSense Billing is the ‘ReadOnly’ role group (shown in the image above). This is a core role group that grants the user read only access to all menus and screens but no rights to modify anything.

To define different default role group permissions for the role groups created when groups are pushed from Azure you can simply create a new role group in LogiSense Billing with the desired permissions and enable the ‘SCIM Default’ setting on the new group. For instance, you may wish the default permissions for groups pushed from Azure to be limited to read-only access to the home and account menus only.

After the Azure groups are pushed to LogiSense Billing and the SCIM Role groups are automatically created you can then access LogiSense Billing and modify the particular SCIM Role Group’s permissions as needed (i.e. grant additional permissions beyond what the SCIM Default role group has provided).

Configure SCIM Provisioning in Azure AD

1. In the Azure portal access your application and click on the Provisioning link on the left sidebar

   

2. Click Get Started

3. Set the Provisioning Mode to Automatic

4. Under Tenant URL enter the URL used to access your LogiSense Billing instance appended with the path /ResourceServer/api/SCIM

5. Under Secret Token enter the SCIM Access Token that was copied from LogiSense Billing
   

   

6. Click Test Connection to verify the Application can connect to LogiSense Billing

   

7. Click Save

8. Once the provisioning settings are saved click the X to close the provisioning page

Creating Users & Groups in Azure

1. Access the Azure portal and load your application

2. Click on Users and Groups on the left sidebar

   

3. Click on Add user/group

   

4. Search/select and assign an existing Azure AD user if you haven’t already added a user or test user

5. To test the integration provisioning the user. Access the

6. To test, you can force an update through the Provision On Demand tab. Access the Provisioning page using the left sidebar

   

7. Click on Provision on demand

   

8. Search for the user you wish to provision and click the Provision button

9. The Azure portal should display no errors and LogiSense Billing should display the new user that has been pushed to it

   

10. In the Azure portal you can follow the same process to provision additional users and groups as needed. Once these entities are created in LogiSense Billing you can configure the permissions for the role groups that you have pushed in order to define what Azure users in those groups can do in the LogiSense Billing application

    

Login to Test SSO Integration

1. Log out of LogiSense Billing

   

2. On the Login page a new Log in with SSO option will be available

   

3. Click on Log in with SSO

4. You will be redirected to the Azure login page

   

5. Enter your Azure AD email and password and click Sign In

6. After entering valid login credentials, you will be directed to the LogiSense Billing application and logged in

The signed in user will now be able to view/modify all of the screens in LogiSense Billing that their role group configuration permits them to access.