Skip to main content

Create a Security Service

You can create a Security service in native IIS, remote IIS, and Docker.

What do you want to do?

Create a Security Service in Native IIS

When you deploy a Security service in native IIS, GroupID does the following:

  • It creates a directory with the Security service’s name at the following physical path on the GroupID server, and copies the service files from its template directory to the new service directory:
    X:\Program Files\Imanami\GroupID 11.0\GroupIDSecurityService\Inetpub\
    (X represents the GroupID installation drive)
  • It also creates a virtual directory for the service in your desired IIS site.

The Security service runs within a virtual directory in IIS while the service files are physically located on disk.

To create a Security service:

  1. In Admin Center, click Applications in the left pane.

  2. Click Add Application.

  3. On the next page, select Security Service and click Next step.

  4. On the Create GroupID Application page, make sure the IIS tile is selected.

  5. In the Application Name box, enter a name for the service or use the default name. The Security service is displayed with this name in GroupID.

  6. In the Deployment Name box, enter a deployment name for the service. The application name and deployment name are displayed on the service card, as shown below:

    ss_card

  7. In the IIS Application Name box, enter an IIS deployment name for the service. This name is used to name the service’s directory in IIS and its physical directory under X:\Program Files\Imanami\GroupID 11.0\GroupIDSecurityService\Inetpub\ on the GroupID server.
    (X represents the GroupID installation drive)
    The IIS application name should be unique for each Security service deployed in IIS.

  8. In the IIS Site drop-down list, select a website to host the service files.
    The list displays the websites defined on the local IIS server. GroupIDSite11 is the default selection.

  9. In the Data Service drop-down list, select a Data service to bind to this Security service.
    A Security service needs a Data service to perform various tasks, such as authentication and multifactor authentication.

  10. Click Create Application.
    The Security service is created and displayed on the Security Service tab.

Create a Security Service in Remote IIS

You can deploy a Security service within a site in remote IIS. For this, you need to connect with the Microsoft IIS Administration API running on the remote IIS machine.

When you create a Data service in remote IIS, GroupID does the following:

  • It creates a virtual directory for the service in a preconfigured site in remote IIS.
  • It creates a physical directory for the service in the folder that is mapped to this preconfigured site.

The Security service runs within a virtual directory in remote IIS while the service files are physically located on disk.

To learn about the remote IIS settings and configurations before deploying a service there, see the Prerequisites for Deployments in Remote IIS topic.

To create a Security service:

  1. In Admin Center, click Applications in the left pane.
  2. Click Add Application.
  3. On the next page select Security Service and click Next step.
  4. On the Create GroupID Application page, select the Remote IIS tile.
  5. In the Application Name box, enter a name for the service or use the default name. The Security service is displayed in GroupID with this name.
  6. In the Deployment Name box, enter a deployment name for the service. The application name and deployment name are displayed on the service card.
  7. To enter information for API URL, Access Token, Username, Password, IIS Application Name, and Website, refer to steps 7-11 in the Create a Portal in Remote IIS topic. Replace any reference to the portal with the Security service.
  8. In the Data Service drop-down list, select a Data service to bind to this Security service.
    A Security service needs a Data service to perform various tasks, such as authentication and multifactor authentication.
  9. Click Create Application.
    The Security service is displayed on the Security Service tab.

Create a Security Service in Docker

GroupID enables you to deploy a Security service in Docker. For this, you need to connect with the API running on a Docker deamon in your environment, so that GroupID can create a container for the service there and run the service from within that container.

For an overview on application deployment in Docker, see the Prerequisites for Deployments in Docker topic.

NOTE: To host the Security service, Docker daemon should be configured to run Windows containers.

To create a Security service:

  1. In Admin Center, click Applications in the left pane.
  2. Click Add Application.
  3. On the next page, select Security Service and click Next step.
  4. On the Create GroupID Application page, select the Docker tile.
  5. In the Application Name box, enter a name for the Security service or use the default name. The service is displayed in GroupID with this name.
  6. In the Deployment Name box, enter a deployment name for the service. The application name and deployment name are displayed on the service card.
  7. To enter information for Port, Service URL, and Container Name, refer to steps 7-9 in the Create a Portal in Docker topic. Replace any reference to the portal with the Security service.
  8. In the Data Service drop-down list, select a Data service to bind to this Security service.
    A Security service needs a Data service to perform various tasks, such as authentication and multifactor authentication.
  9. Click Create Application.
    The Security service is created and displayed on the Security Service tab.

Launch a Security Service

  1. In Admin Center, select Applications in the left pane.
  2. On the Security Service tab, click Launch Application for a service. The GroupID Applications page is displayed. Options on this page are discussed in the Access your Applications topic. Any actions you perform will be carried out through the respective Security service.

See Also