KACE as a Service 7.1 - Administrator Guide

You can use Quest Identity Broker (QIB) to enable users to log in to the Administrator Console and User Console using credentials from third-party identity providers, such as your organization's Identity Provider and Microsoft Azure™ Active Directory.

QIB can be enabled for a single organization only. If the Organization component is enabled on your appliance, you can enable QIB for the default organization only. To use single sign on with multiple organizations, use Active Directory authentication. See Configure Active Directory as the single sign on method.

Go to the appliance Control Panel:

◦

If the Organization component is not enabled on the appliance, log in to the K1000 Administrator Console, http://K1000_hostname/admin, then click Settings.

◦

If the Organization component is enabled on the appliance, log in to the K1000 System Administration Console, http://K1000_hostname/system, or select System in the drop-down list in the top-right corner of the page, then click Settings.

In the Single Sign On section of the Security Settings page, select Quest Identity Broker, then provide the following information:

Option

Description

Web Server Assertion Consuming Service URL

The URL associated with your K1000 appliance. This URL is created automatically during appliance configuration. To enable QIB, contact Quest Support and provide this URL to obtain the Relying Party Identifier for your appliance.

IMPORTANT: If you enable or disable SSL for the appliance, this URL changes. As a result, you need to provide this URL to Quest Support and obtain a new Relying Party Identifier any time SSL settings are changed.

Relying Party Identifier

A unique identifier provided by Quest Support to enable QIB. This identifier determines which identity provider, such as your organization's Identity Provider or Microsoft Azure Active Directory, is used for authentication. You must provide your Web Server Assertion Consuming Service URL to Quest Support to receive this identifier.

Automatically approve user requests

Users requesting single sign on access are automatically granted access to the K1000 User Console if they are authenticated by the third-party identity provider. Accounts for these users are created automatically on the K1000 appliance.

Manually approve user requests

Administrators must approve access requests before users can access the K1000 Administrator Console or User Console. When users attempt to sign on to the K1000 using third-party credentials, the K1000 creates approval requests. When administrators log in to the Administrator Console, a notification stating that approval requests are pending appears on the information bar at the top of the Dashboard page. When administrators approve requests, user accounts are created on the K1000 appliance and users can access the K1000 Administrator Console or User Console.

To specify identity provider settings, click Advanced Settings.

NOTE: Do not change these settings unless directed to do so by Quest Support.

Option	Description
Quest Identity BrokerURL	The URL of the identity provider.
Quest Identity BrokerIdentifier	The unique identifier of the identity provider.
Quest Identity BrokerCertificate	The certificate used to verify communications with the identity provider.

Click Save and Restart Services.

Generate an SSL certificate

You can generate a self-signed SSL certificate, or generate a certificate signing request for third-party certificates, using the Administrator Console.

Go to the appliance Control Panel:

◦

If the Organization component is not enabled on the appliance, log in to the K1000 Administrator Console, http://K1000_hostname/admin, then click Settings.

◦

Click Security Settings to display the Security Settings page.

In the SSL section, click Enable SSL.

Additional SSL options are displayed.

Click SSL Certificate Form to display the SSL Certificate Form page.

NOTE: If a certificate signing request has previously been generated, it appears on the page. To generate a new request, you need to update the information in the Configure section, then click Save before you click Generate Self-Signed Certificate.

In the Configure section, provide the following information:

Option	Description
Company Name	The name of your company.
Organization Name	The name of your organizational unit or business group.
Common Name	The common name of the appliance you are creating the SSL certificate for.
Email	Your email address.
City Name	The name of your locality.
State or Province Name	The name of your state or province.
Country Name	The name of your country.

Click Save.

If this is the first time the SSL Certificate Form has been saved, the Certificate Signing Request section appears. If the form has previously been saved, the Certificate Signing Request section is updated.

Do one of the following:

◦

To generate a certificate using a third-party certificate issuer:

Copy all of the text in the Certificate Signing Request section, including the lines "-----BEGIN CERTIFICATE REQUEST-----" and "-----END CERTIFICATE REQUEST-----" and everything in between, then send it to the certificate issuer or the person who provides your company with web server certificates.

When you receive a certificate from the third party, return to the Security Settings page and upload the certificate. See Configure security settings for the appliance.

◦

To generate a self-signed certificate:

Click Generate Self-Signed Certificate to generate and display the certificate below the Certificate Signing Request section.

Click Deploy Self-Signed Certificate, then click Yes.

On the Security Settings page, click Save and Restart Services.

Self-signed certificates are converted to PEM files, named kbox.pem, and the files are placed in K1000 Agent data folders.

NOTE: Your private key appears in the Private Key field. It is deployed to the appliance when you deploy a valid certificate. Do not send the private key to anyone. It is displayed here in case you want to deploy this certificate to another web server.

NOTE: The certificate and private key for SSL are not included in the appliance’s daily backups for security reasons. Retain these two files for your own records.