Service Types

Follow these steps to register a new Service Type in your K2 environment.

1. Click New in the Service Types section.
   
2. The Configure Service Type page opens.
   
3. Configure the Service Type. Configuration values are determined by the selected Service Type.
   The list of names are based on .NET Reflection, where K2 will iterate over assemblies in the ServiceBroker directory on the K2 server (default: "%ProgramFiles%\K2 \ServiceBroker") and return those assemblies that implement the necessary Service Broker/Type Interfaces
4. Click OK

Follow these steps to edit a Service Type.

1. Select a Service Type from the list and click Edit.
   
2. The Configure Service Type page opens. Edit the values as necessary, using the table in Registering a Service Type as a guide.
   
3. Update fields as required, and click OK.

Follow these steps to delete a Service Type.

1. Select a Service Type and click Delete.
   
2. The Delete dialog opens. Click OK to confirm you wish to delete the Service Type.
   
3. Click OK.

Follow these steps to create a new Service Instance for a Service Type:

1. Click on the Service Type you want to create a new instance for.
2. The New Instance button becomes available.
   
   
3. Click New Instance. The Configure Service Instance page opens.
   

   Use the table below as a guideline to configure the new service instance:

   Section	Field	What to do
   Service Instance	Display Name	Type a value for the display name of the new service instance.
   Service Instance	Description	Type a value to describe the new service instance.
   Service Instance	Service Type	The Service Type selected from the previous view will display. You can select a different Service Type from the drop-down if needed.
   Service Authentication	Authentication Mode	Select the Authentication Mode to be used for this service instance from the drop-down. This setting determines the security credentials that will be used to connect to the underlying system. See the topic Authentication Modes for more information. Not all Authentication Modes are supported for all Service Types. Refer to the Service Type documentation for the particular Service Type you wish to configure to see what known Authentication Mode restrictions may exist. Impersonate: passes the connected user's credentials to the underlying system OAuth: uses OAuth tokens to authenticate with the underlying system. This setting requires a configured OAuth resource for the underlying system. ServiceAccount: connects to the underlying system using the credentials of the account that runs the K2 application service SSO: uses cached Single Sign-On credentials for the connected user. This setting will require you to select a Security Provider that will map an incoming user's credentials to alternate credentials that are accepted by the underlying system. Static: use a static username and password to connect to the underlying system
   Service Authentication	Security Provider	The Security Provider drop-down will be enabled when the single sign on (SSO) Authentication Mode was selected. Select the security provider to be used from the drop-down.
   Service Authentication	OAuth Resource Name	This drop-down will be enabled when the OAuth Authentication Mode was selected. Select the OAuth resource name to be used from the drop-down.(The Resource is defined using the Authentication section of the K2 management site.)
   Service Authentication	OAuth Resource Audience	Enter the OAuth Resource Audience URI to use for OAuth Authentication. This setting is only applicable when using the OAuth Authentication Mode, and refers to the URI used to access a realm, for example https://graph.windows.net
   Service Authentication	User Name	This field will be enabled when the Static Authentication Mode was selected. Type the name of the user to be used when connecting to the underlying system.
   Service Authentication	Password	This field will be enabled when the Static Authentication Mode was selected. Type the password of the user entered in the User Name field.
   Service Authentication	Extra	Type a value for extra connection information. This setting is usually not required unless the authentication mechanism or Service Type selected requires or allows additional configuration.
   Service Authentication	Enforce Impersonation	This is a Pass-through Authentication option and is only applicable for the Impersonate and OAuth Authentication Modes. If Enforce Impersonation is not checked and Pass-through Authentication fails for the impersonated user, the service will revert to the K2 Service Account and retry the operation. If Enforce Impersonation is checked, the service will not revert to the Service Account if it fails with the impersonated user.
   Service Keys	(The Service Keys depends on the Service Type selected).	Provide the configuration settings for the particular Service Type you are configuring. See the documentation for the particular service type for more information on the available configuration values for that Service Type.
   SmartObjects	Generate SmartObjects for this Service Instance	Select the check box if you want to automatically generate SmartObjects for the new Service Instance. (Whether this check box is selected or not, designers can still create SmartObjects for the underlying system manually using K2 Design tools).

4. Click OK to register the new Service Instance after providing the necessary values. It may take a few seconds for this operation to complete, since K2 may be performing discovery operations against a large set of entities, and/or generating and publishing SmartObjects, if the Generate SmartObjects option was selected.

The Security button allows you to define design-time rules to control who is allowed to manage service types. Service types inherit rights from the service instances security level. See Authorization Framework Overview and Service Instances Security for more information about rights, inheritance, considerations, and best practices before assigning rights per service type.

You can assign rights to a specific service type, which allows you more granular control for each service type.

Follow these steps to add rights to a specific service type:

1. Select a service type and then click Security.
   

2. Add a user, group, or role by clicking the Add button.
   
3. On the Add Users, Groups, And Roles page search and add a user, group, or role. Click OK.
   
4. Specify the user, group, or role's View, Create, Modify, Delete, and Security rights. If the user, group, or role has rights at the service instances security level, the following rights are available: Allow, Deny and Inherited Allow. If the user, group, or role does not have rights at the service instances security level or if the inheritance is broken the following rights are available: Allow, Deny and None.
   
5. Add more users, groups, and roles if necessary. Click Close.
   When specifying users, groups, and roles, the Everyone role is added during installation, providing all authenticated users, the ability to view service types and service instances. Best practice would be to modify the Everyone role's view rights to None on the Service Instances Security level, and grant permissions to users, groups, and roles according to your organizations requirement on the service type and service instance.

Follow these steps to edit service type rights:

1. Select the service type and click Security.
2. Select a user, group, or role and edit the rights. Click Close.
   

Follow these steps to remove edit service type rights:

1. Select the service type and click Security.
2. Select a required user, group, or role and click Remove.