Last updated: May 06, 2024
Okta
An Identity Provider (IdP) vouches for the identity of a person through the use of an authentication token. Vasion Print (formerly PrinterLogic) uses IdP for several things, including logging in to the Admin Console and portals, deploying printers, releasing print jobs, and more.
If you use an IdP, the Control Panel Application (CPA) only supports badge and PIN authentication.
These steps follow Okta's classic user interface rather than the Developer Console user interface.
Configure Connection
To add and configure enterprise app properties for the Vasion Print (formerly PrinterLogic) connection do the following:
- Create Okta App.
- Add IdP Template.
- Configure Single Sign On.
- Add the X-509 Certificate.
- Complete IdP Settings.
- Configure Provisioning.
- Add Vasion Print (formerly PrinterLogic) Admins.
1. Create Okta App
- Log into your Okta Admin Portal.
-
In the left-side menu, expand Applications and select the Applications option.
- Select Browse App Catalog button.
- In the Search field, type PrinterLogic.
- Select PrinterLogic SaaS (with support for multiple instances).
- Select the Add Integration button.
- In the Application label field, type the name you want to give the app.
- Select your instance region from the Region drop-down.
- Enter your subdomain in the Subdomain field.
- Select Done in the lower-right.
Leave the current browser open to the new app page. To continue the app configuration, you need to open another browser and open the
If the IdP Settings page does not look like the image shown below, you may not be using the latest version and should contact Product Support to upgrade your IdP settings.
2. Add IdP Template
- In a separate browser tab, open your Vasion Print (formerly PrinterLogic) Admin Console and sign in.
- Select Tools Settings General, and scroll down to the Identity Provider Settings section.
- Select IdP, and then select Add.
- Select the identity provider you want to configure in the IdP Template drop-down.
- Select SAML2 in the Authentication Protocol section.
-
In the Provisioning section if you are using SCIM, leave the JIT option unchecked.
By default, it is assumed you are using SCIM for provisioning. Only select JIT if SCIM is not being used.
- In the Name field, enter the name you want displayed on the login button for users, e.g. My Company, Login, Acme Corp, etc.
- Scroll down and select the desired enable setting(s).
- Enable for End Users Login — Allows end users to login using this IdP. (Self-service Portal)
- Enable for Admin Login — Allows Admin users to login using this IdP. (Admin Console)
- Both boxes can be checked when using a single IdP, or if the admin and end users use the same IdP to log in.
Keep the IdP Settings screen open so that the Service Provider Information at the bottom is available for the following steps.
3. Configure Single Sign On
- Select the Sign On tab of the Okta app, then select the Edit link on the right.
- Copy the Vasion Print (formerly PrinterLogic) Relay State from the Service Provider Information section and paste it into the Okta app's Default Relay State field.
- Scroll down to the Okta app's Advanced Sign-on Settings section.
- Copy the Vasion Print (formerly PrinterLogic) IdP Identifier and paste it into Okta's IDP ID field.
- Select Save
-
Select View SAML Setup Instructions. A new window displays with the information to copy and paste into Vasion Print (formerly PrinterLogic).
-
In Okta's View Setup Instructions window, copy the Login URL/SignOn URL and paste it into the Vasion Print (formerly PrinterLogic) SSO URL field.
- Press Tab to auto-populate the Issuer URL and Issuer ID fields.
4. Add the X-509 Certificate
- Return to Okta's View Setup Instructions window and copy the main body of the X-509 Certificate in PEM Text Format.
-
Paste it into the Vasion Print (formerly PrinterLogic) X-509 Certificate field.
- Select Apply.
-
Select Save
The Admin Group Name field will be left blank unless you are using an Attribute Statement for additional security. Steps to configure that are found in Additional Admin Console Security , and can be setup after the initial IdP configuration.
5. Complete IdP Settings
- On the Vasion Print (formerly PrinterLogic) General page, navigate back to the Identity Provider Settings section.
-
To have Vasion Print (formerly PrinterLogic) prompt your users to authenticate through the IdP when performing any function requiring authorization, such as installing a printer, select the Automatically Open Browser to Login on Desktop Client option.
If this option is not selected, the user must manually navigate to the IdP login screen to sign in.
-
We recommend enabling the Use Loopback with SAML2 option. The IdP needs to provide an authentication token to the desktop clients whenever authentication happens. This option allows the client to handle the token and automatically log in without interaction from end users.
- The option to Use Domain User (Windows only) will automatically authorize domain-joined Windows users and not require login via the configured IdPs.
- Select Save in the top-right corner of the General page.
6. Configure Provisioning
The provisioning steps vary depending on whether you are using SCIM or JIT provisioning. Please choose the appropriate option below to view the corresponding steps for the method you are using.
SCIM Provisioning
Enable SCIM Provisioning
- Return to the Okta portal and select the app's Provisioning tab.
- Select Configure API Integration.
- Select Enable API Integration.
Generate / Apply SCIM Token
- In the Vasion Print (formerly PrinterLogic)General settings, select the SCIM option in the Identity Provider Settings section.
- Select your IdP configuration in the drop-down menu.
-
Select Generate SCIM Token.
Generating a SCIM token invalidates any previous tokens for that IdP.
- Select Proceed.
- Copy the token, close the modal, and select Save at the top-right corner of General settings.
- Paste the token into the Okta Provisioning tab's API Token field.
- Select Test API Credentials. A notification displays if the token was verified successfully.
- Select Save in Okta.
Enable the To App Settings
- Select To App in the left-side Settings menu.
- Select the Edit link to the right.
- Check the Enable box for the following.
- Create Users.
- Update Users.
- Deactivate Users.
- Select Save in the lower-right.
Assign Users / Groups
Please note that Okta does not support assigning the same groups on the Assignments and Push Groups tabs. For example, if you assign "Group A" on the Assignments tab you should not assign "Group A" on the Push Group tab.
The recommended best practice is to create an Okta group that includes all users who will need access to the Vasion Print (formerly PrinterLogic) application, which should consist of admin users who require access to the Vasion Print (formerly PrinterLogic) Admin Console as well as end users who only need access to the Vasion Print (formerly PrinterLogic) Self-service Portal. Assign this group on the "Assignments" tab in Okta, which will provision all the necessary user records into Vasion Print (formerly PrinterLogic) without any group membership data. You can then assign your role-specific groups (Admin, Help Desk, etc.) on the "Push Group" tab, which will provision the group membership data needed for RBAC, Portal Security, and Deployment rules in Vasion Print (formerly PrinterLogic).
For reference, see the official Okta documentation on the Push Group tab.
Assignments Tab: Assign Users / Groups
- Select the Okta app's Assignments tab.
-
Select the Assign drop-down.
- To grant access for individual users, select Assign to People. To grant access for groups select Assign to Groups.
- Search for the desired users / groups and select Assign.
- Select Done.
- Repeat these steps for any additional users / groups.
Push Groups Tab: Assign Groups
If you need to provision group membership information into Vasion Print (formerly PrinterLogic).
- Select the Okta app's Push Groups tab.
- Select + Push Group.
-
Select Find groups by name.
-
Search for and select the desired group(s).
Ensure that the groups selected on this tab are NOT the same group/s assigned on the "Assignments" tab. -
Under the Match result & push action section verify that + Create Group is selected.
- Select Save.
- Under Push Status, verify that the status changes from Pushing to Active.
- Exit Okta.
JIT Provisioning
Assign Users
NOTE: When using JIT, the provisioning of group membership associations is not supported. This means you will not be able to configure RBAC roles, printer deployments or portal security roles to groups in Vasion Print (formerly PrinterLogic). All assignments will have to be done to users individually.
User Creation
If you wish to use JIT Provisioning, make sure the JIT option in the IdP Settings modal is checked and do not enable SCIM. Doing so will create duplicate users and impact login and user authentication.
JIT does not support the provisioning of group membership associations, so you cannot apply RBAC roles, printer deployments or portal security roles to groups. All assignments have to be done individually for each user.
When using JIT Provisioning, the application creates users during the first sign-in attempt.
- Access your Vasion Print (formerly PrinterLogic) instance and select Sign in with <IdP Name>.
- Attempt to login with your IdP credentials.
-
This login attempt will fail and return you to the Vasion Print (formerly PrinterLogic) login page.
This is expected. With JIT, this action triggers the user creation in Vasion Print (formerly PrinterLogic).
- The following login attempt with valid credentials initiates a typical login sequence.
Administrators who need access to the Admin Console still need to be added to the Tools Users page using the steps in Admin Console Users.
7. Add Vasion Print (formerly PrinterLogic) Admins
For steps on assigning users and roles to the Vasion Print (formerly PrinterLogic) Admin Console reference Admin Console Users.
-
Released: October 31st, 2024
-
Released: October 29th, 2024
-
Android: October 28th, 2024
-
Released: October 12th, 2024