Integration
Integration is a service that sets up and manages authentication services and account information for various applications.
In SCP SingleID, we support integration with new applications through customized authentication linkage and account distribution services, as well as the DIY (Do-It-Yourself) feature.
Through the integration menu, we provide integration management features such as Application, Identity Provider, Authenticator, MFA Service Provider.
Application
The application is a menu that registers and connects various applications to apply the authentication service of SCP SingleID.
The administrator can register/modify a new application through the application list screen, and can sort, search, and delete registered applications.
Application List
The administrator can select a registered application on the application list screen to edit/delete, sort, search, etc., and can navigate to a menu screen where a new application can be registered.
To check the application list, access the menu as follows.
- Admin Portal > Integration > Application
| Category | Description |
|---|---|
| Name | This is the name of the application. It can be entered when creating the application. |
| Type | Classified by application integration protocols as SAML, OIDC, SCIM. |
| Display | This is a displayed item in the User Portal application list.
|
| Status | It is the application status. It is divided into active and inactive.
|
| All button | Displays all active and inactive applications in the list. |
| Active button | Only active applications are displayed in the list. |
| Inactive button | Only inactive applications are displayed in the list. |
| Search term input field | You can search the application list. After entering a search term, click the magnifying glass icon or press Enter to perform the search.
|
| Detail button | Detailed search is possible. Search conditions can be combined with AND. After entering multiple fields and clicking the ‘Search’ button, the search is performed according to the conditions.
|
| Download button | SAML metadata download is available. You can download the SAML metadata files for the internal network and the internet network. |
| Register button | You can register a new application. |
Application Registration
The administrator can register the application by clicking the Register button on the list screen.
Application registration is possible in two ways: Custom App Integration and Pre-Built App Integration.
To register an application, access the menu as follows.
- Admin Portal > Integration > Application > Register Button Click
- Custom App Integration or Pre-Built App Integration Select tab
Custom App Integration
Custom App Integration registration is a connection menu for authenticating the application you want to integrate and distributing accounts.
We provide three types of connection functions as follows.
When you want to register an application by linking authentication, you provide and select the type (SAML, OIDC) according to the standard authentication linkage method.
When registering an application by linking account distribution, we provide the standard online API method (SCIM).
The integration features provided by SingleID can be classified as follows, and the information input and configuration steps differ depending on the required integration scope. When setting up the standard authentication integration methods SAML and OIDC, if account provisioning is not selected, the attribute integration step is omitted, shortening the registration process.
| Standard Protocol | Authentication linkage, account deployment linkage | Authentication linkage | Account deployment linkage |
|---|---|---|---|
| SAML | ○ | ○ | - |
| OIDC | ○ | ○ | - |
| SCIM | - | - | ○ |
To register the application Custom App Integration, follow the steps below.
- Admin Portal > Integration > Application > Register Click button
- Custom App Integration > Web Application(SAML) orWeb Application(OIDC) or Identity Provisioning(SCIM v2.0) select > Next click the button
- Go to detailed settings
Through a screen consisting of six steps as follows, you can enter and configure the information required for integration and register the application.
Applications using standard protocols (SAML, OIDC, SCIM) can register information and set policies and attributes through a screen consisting of the following six steps.
General
Enter the general application information by referring to the below.
| Category | Description | Required? |
|---|---|---|
| Name | Enter the application name. | Required |
| Description | Enter description of the application. | Select |
| Logo Image | Register logo. (File upload or URL link) | Select |
| Screen display | Displayed to the user on the User Portal. | Select |
| Access URL | Enter the application access URL. | Required |
| Auto Logout | Set auto logout according to session policy. | Select |
| Automatic Redirection | Set to automatically move to the Service Provider after logout. | Select |
| Logout URL | Enter the URL address to navigate to after logout (if not entered, use Access URL) | Optional |
SSO
On the SSO information input screen, enter Single Sign On configuration information.
| Category | Description | Required |
|---|---|---|
| Issuer | Enter the unique identifier value of SP. | Required |
| Single Sign-On URL | Enter Full URL for login. | Required |
| Logout URL | Enter SLO Return URL. | Optional |
| Logout Method | Provides Back-Channel Logout, Front-Channel Logout (HTTP Redirect Binding), Front-Channel Logout (HTTP POST Binding). | Required |
| Response Signing | SAML Response signing setting. | Select |
| Validation On-Request | Setting whether to use Signature Validation. | Select |
| Encryption | Encryption application setting. | Select |
| Application Certificate | Certificate registration (PEM format) | Required |
| Attribute to map during SSO | Select SSO connection attribute information and set a unique value. | Required |
| ‘Metadata File Import’ button | Provides SAML metadata file upload functionality. (Identifies ID provider endpoint and certificate) | Select |
Single Sign-On Settings
- If you select either Validation On Request or Encryption, you must register a certificate. (Register the certificate value exported as Plain Text)
- Attribute to map during SSO Information can be added by clicking to select attribute information provided by SingleID. Among the selected attributes, a unique value for user identification must be selected as mandatory.
- To deliver SingleID’s Attribute information to the connected target application, you can align the SingleID attribute name to the attribute name that will be mapped in the application and deliver it. This communication information exchanged during authentication is called claim (Claim) information, and the received information is used by the SP to set permissions or as attribute information for operation and management.
Provisioning
The Provisioning menu is an account management function that can distribute user information to applications for synchronization. In SingleID, we provide methods based on global standard API specifications such as SCIM and REST.
On the Provisioning information input screen, enter the configuration information for account information distribution.
| Category | Description | Required? |
|---|---|---|
| Provisioning Configuration | If you want to use account information synchronization, please click the On button. If you select Off, you can skip account synchronization. | Required |
| Base Address | Enter the Base Address (URL) that defines the Endpoint of the target system supporting the SCIM API. | Required |
| Accept | Enter the Accept (e.g., application/json) information, which is the HTTP Accept Header value used in SCIM REQUEST. | Required |
| Content Type | Enter the Content Type (e.g., application/json), which is the HTTP Content Type header value used in SCIM REQUEST. | Required |
| User Name | Registers the User Name used for authentication to the target REST service. | Required |
| Password | Set the password used for authentication to the target REST service. | Required |
| Bearer Token | Register the Bearer Token used when calling the API (for authorization). | Optional |
| Client ID | Register the Client ID. The Client ID is an ID issued by the authentication server to a registered client, and because the Client ID itself is information disclosed to the resource owner, it should not be used alone for client authentication. | Optional |
| Client Secret | Register the Client Secret information. Client Secret is a secret information generated by the authentication server, a unique value known only to the authentication server. | Optional |
| Access Token Node ID | Register Access Token Node ID. Access Token Node ID is the Field ID of a JSON Object Node, returned from the target Access Token REST service, and includes the Token value. Access Token is used for the purpose of authorizing access to resources. It is important that the resource server only accepts Access Tokens from the Client. | Optional |
| Access Token Base Address | Register the Access Token Base Address (URL) required to receive an Access Token as the Base Address of the target REST service. | Optional |
| Access Token Content Type | Registers the Access Token Content Type (e.g., application/x-www-form-urlencoded), which is the HTTP Content-Type header value of the target Access Token REST service. | Required |
| Provisioning | Select one of user or group as the default target for provisioning, and if necessary, you can select both user and group. | Select |
| Inbound Provisioning Schedule | Click On to register periodically (hour, day, month, year) through Intbound Provisioning Schedule | Select |
| Outbound Provisioning Schedule | Click On to register the Outbound Provisioning Schedule. Click Off to deploy in real time. | Select |
Profile
Enter the setting information for user/group for deployment on the profile information input screen.
| Category | Description | Required |
|---|---|---|
| Profile name | Enter the profile name. | Required |
| Description | Register a description for the profile. | Optional |
| Attribute | Click Add to select and enter attribute information. | Select |
Profile Mapping
- Provisioning target selection tab menu, click User, Group to add properties.
- Click Profile Mapping to match and connect the required information in the target application based on the SCIM schema information.
- Provides a feature that allows you to configure the creation of an execution script that can perform real-time conversion when running provisioning (a conversion script based on the JEXL standard script). However, there is no validation check function as it receives and executes as entered.
After entering all items and clicking the Complete button, the basic application settings are completed. When you complete registering a new application, it will be added to the application list and new tabs called Policy, Assignment will be created.
Policy
You can set login policy and access control information for application policy configuration.
| Category | Description | Required? |
|---|---|---|
| Login Policy | Set the login policy applied when logging into the application. To set it, please assign the application in the Login Policy to be configured. | Select |
| Access Control | This is a setting that allows the user to control access to the app. When enabled, you can set whether to request access permission for the application and whether it is approved. | Select |
Allocation
Register information for assigning application users based on users and groups. This menu assigns access permissions by setting the users and groups that can access the registered application.
If you want to assign a user, follow the steps below.
- If you click the application, you will be taken to the detailed page of that application.
- Click the Assign tab and User tab > Assign button
- User Assignment When the popup appears, select the user you want to assign, and click the Assign button.
- Assignment tab shows the selected user in the list.
Similarly, you can assign a predefined group via the Group tab’s Assign button. Assign the group using the same method.
Group Settings
- When setting groups that can access the application, configure it to include information that defines specific groups for distinction.
- You must define rules and groups in advance so that you can manage access permissions with member rules that can distinguish groups.
Application status
Activation (Active): Exposes the application in the User Portal, and by configuring Sign-On services, provisioning, policies, etc., it is a state where users can access and use the application.
Inactive: It does not expose the application on the User Portal, and it is a state where the application can be deleted.
Delete: When deleting a registered application, caution is required. Therefore, a popup is displayed to allow you to verify the application information and status once more.
Pre-Built App Integration
Pre-Built App Integration menu provides a convenient way to quickly and easily connect the SaaS application you want to use, by pre-preparing necessary settings such as connection information, name, icon, so you can use it conveniently.
To integrate the application via Pre-Built App Integration, check the menu path below.
- Admin Portal > Integration > Application > Register > Pre-Built App Integration Click tab
- Application select > Next button click
- Go to detailed settings
Pre-Built App Integration menu, like the Custom App Integration menu, can register an application by entering and configuring the necessary integration information through a screen consisting of six steps as follows.
The input items and methods for each step are the same, except for the information that has been predefined and entered for Pre-Built.
General
Enter the general application information by referring to the below.
| Category | Description | Required? |
|---|---|---|
| Name | Enter the name of the application. | Required |
| Description | Enter a description of the application (e.g., tasks, usage, etc.). | Optional |
| Logo Image | Register a logo that can intuitively identify the application. There are file upload and URL link methods. | Optional |
| Screen display | When selected, it is shown to the user in the User Portal. | Select |
| Access URL | Enter the application’s Access URL. For the application to access, enter the login page. | Required |
| Auto logout | When selected, it will be automatically logged out without re-confirmation according to the session policy. | Select |
| Automatic Redirection | When selected, it moves to the Service Provider without displaying the logout completion page. | Select |
| Logout URL | Enter the URL address to navigate to when the user logs out. If left blank, it will be set to the Access URL address. | Optional |
SSO
Enter Single Sign On setting information on the SSO information input screen.
| Category | Description | Required |
|---|---|---|
| Issuer | Enter the Issuer, which is the unique identifier of the SP (Service Provider) and the value verified by the Response Issuer. | Required |
| Single Sign-On URL | Enter the Single Sign-On URL, which is the full URL required when logging into the system. | Required |
| Logout URL | Enter the Logout URL, which is the URL value for SLO (Single Logout) Return. | Optional |
| Logout Method | The logout methods for SLO (Single Logout) Return are provided in three ways as follows.
| Required |
| Response Signing | If you want to sign the returned SAML Response after the authentication process, use Response Signing. | Select |
| Validation On-Request | Check to use Signature Validation. | Select |
| Encryption | Select whether to apply Encryption. | Select |
| Application Certificate | If you select one of Validation On Request or Encryption, you must register a “certificate”. Please enter a valid value according to the PEM (Privacy-Enhanced Mail) format. | Required |
| Attribute to map during SSO | Select the attribute information required for SSO connection and set a unique value for user identification. ※ The ‘Next’ button is activated only after selecting a Subject Attribute. | Required |
| ‘Metadata file import’ button | The SAML metadata file contains information about various SAML identity providers that can be used for SAML 2.0 protocol message exchanges. This metadata identifies the IdP endpoints and certificates to secure SAML 2.0 message exchanges. When you click ‘Import metadata file’, you can upload a file. | Select |
Single Sign-On Settings
- If you select either Validation On Request or Encryption, you must register the certificate. (Register the certificate value exported as Plain Text)
- Attribute to map during SSO Information can be added by clicking and selecting attribute information provided by SingleID. Among the selected attributes, a unique value for user identification must be selected as mandatory.
- To deliver SingleID attribute information to the connected target application, you can align the SingleID attribute name to the attribute name that will be mapped in the application and deliver it. This information communicated during authentication is called claim (Claim) information, and the SP uses the received information to set permissions or as attribute information for operation and management.
Provisioning
The Provisioning menu is an account management function that can distribute user information to applications for synchronization. In SingleID, we provide methods based on global standard API specifications such as SCIM and REST.
Enter the configuration information for account information distribution on the Provisioning information input screen.
| Category | Description | Required |
|---|---|---|
| Provisioning Configuration | Click the ‘On’ button to enable account information synchronization. Selecting ‘Off’ will allow you to SKIP account synchronization. | Required |
| Base Address | Enter the Base Address (URL) that defines the Endpoint of the target system supporting the SCIM API. | Required |
| Accept | Enter the Accept (e.g., application/json) information, which is the HTTP Accept Header value used in SCIM REQUEST. | Required |
| Content Type | Enter the Content Type (e.g., application/json), which is the HTTP Content Type header value used in SCIM REQUEST. | Required |
| User Name | Registers the User Name used for authentication to the target REST service. | Required |
| Password | Set the password used for authentication to the target REST service. | Required |
| Bearer Token | Register the Bearer Token used when calling the API (for authorization). | Optional |
| Client ID | Register the Client ID. The Client ID is an ID issued by the authentication server to a registered client, and because the Client ID itself is information disclosed to the resource owner, it should not be used alone for client authentication. | Optional |
| Client Secret | Register Client Secret information. Client Secret is a secret generated by the authentication server, a unique value known only to the authentication server. | Optional |
| Access Token Node ID | Register the Access Token Node ID. The Access Token Node ID is the Field ID of a JSON Object Node, which is returned from the target Access Token REST service and includes the token value. The Access Token is used for the purpose of authorizing access to resources. It is important that the resource server accepts only the Access Token from the client. | 선택 |
| Access Token Base Address | Register the Access Token Base Address (URL) required to obtain an Access Token as the Base Address of the target REST service. | Optional |
| Access Token Content Type | Registers the Access Token Content Type (e.g., application/x-www-form-urlencoded), which is the HTTP Content-Type header value of the target Access Token REST service. | Required |
| Provisioning | Select one of user or group as the default target for provisioning, and if needed you can select both user and group. | Select |
| Inbound Provisioning Schedule | Click On to register periodically (hour, date, month, year) through Intbound Provisioning Schedule. | Select |
| Outbound Provisioning Schedule | Click On to register the Outbound Provisioning Schedule. Click Off to deploy in real time. | Select |
Profile
Enter the user/group configuration information for deployment on the profile information input screen.
| Category | Description | Required? |
|---|---|---|
| Profile name | Enter the profile name. | Required |
| Description | Register a description for the profile. | Required |
| Attribute | Click Add to select and enter attribute information. | Required |
Profile Mapping
- In the tab menu where the Provisioning target is selected, click User, Group to add properties.
- Click Profile Mapping to match and connect the required information in the target application based on the SCIM schema information.
- Provides the ability to configure an execution script (written as a conversion script based on the JEXL standard script) that can perform real-time conversion when executing provisioning.
However, there is no validation check function as it receives and executes as entered.
After entering all items and clicking the Complete button, the basic application settings are completed. When you complete registering a new application, it is added to the application list and new tabs called Policy, Assignment are created.
Policy
You can set login policies and access control information for application policy settings.
| Category | Description | Required |
|---|---|---|
| Login Policy | Set the login policy applied when logging into the application. To set it, please assign the application in the ‘Login Policy’ to be configured. | Select |
| Access Control | This is a setting that allows the user to control access to the app. When enabled, you can set whether to allow access requests to the application and whether they are approved. | Select |
Assignment Settings
Register information for assigning application users based on User and Group. This menu assigns access permissions by setting users and groups that can access the registered application.
To assign a user, follow the steps below.
- When you click the application, you will be taken to the detailed page of that application.
- Click the Assign tab and the User tab > Assign button.
- User Assignment When the popup appears, select the user you want to assign, and click the Assign button.
- Assignment tab shows the selected user in the list.
Similarly, you can assign a predefined group via the Assign button in the group tab. Assign groups using the same method.
Group Settings
When setting the groups that can access the application, configure it to include information that defines specific groups for distinction. You must define rules and groups in advance so that you can manage access permissions with member rules that can distinguish groups.
Application status
- Activation (Active): Exposes the application on the User Portal, and by setting Sign-On services, provisioning, policies, etc., it is a state where users can access and use the application.
- Inactive: Does not expose the application in the User Portal, and is a state where the application can be deleted.
- Delete: When deleting a registered application, caution is required. Therefore, a popup is displayed so that the application information and status can be checked once more.
Application Modification
You can modify the settings by clicking the application on the list screen.
If you want to modify the application, follow the steps below.
- Admin Portal > Integration > Select Application > Edit Click the button.
- Click the General, SSO, Provisioning, Policy, Assignment, Permission Items, Rebranding tab to edit the items.
- Save button을 클릭하세요.
Permission Items
The permissions tab provides synchronization integration with the application’s permissions.
If you want to set permissions, follow the steps below.
- If you click the application, you will be taken to the detailed page of that application.
- Click the Assignment tab and the Permission Items tab > click the Register button.
- Permission item When the popup window appears, it is necessary to register the permission item.
- Enter Permission, key, display name, content and click Save to register the permission.
Rebranding
When registering in the application, an additional rebranding tab that does not appear is created. The application’s rebranding includes rebranding functionality for the login page when accessing a separate application.
The included rebranding features are as follows.
- Favicon : The favicon can be edited in the browser.
- Header logo: The header logo on the login screen can be changed to the logo you want.
- Key visual image: The key image set by default on the login page can be modified.
- Sign-up page redirection: Registration can be done on a separate operating sign-up page instead of SingleID’s sign-up page.
- Privacy Policy Redirection: You can register the privacy policy URL used in the existing application.
- Terms of Service redirection: You can register the Terms of Service URL used in the existing application.
Rebranding Tab Activation Conditions
The rebranding tab appears in SAML and OIDC target applications.
UI
By clicking the application on the list screen, and clicking the edit button on the rebranding tab, you can configure application-specific UI rebranding.
Favicon Change
Favicon changes in the application can be set according to the characteristics of the corporate application.
If you want to edit the favicon, follow the steps below.
- Admin Portal > Integration > Select Application > UI > Edit Click the button.
- Favicon select custom in the Favicon item.
- Favicon image (pencil shape) Click the item, then click the favicon image.
- Upload an icon file or enter the icon image URL.
- Save button, click it and verify through the preview screen that the upload was successful. 6.Korean page Enter the title in Korean.
- English page Enter in English in the title.
- If the input is completed, check through the right preview whether it was entered correctly.
- Click the Publish button at the lower right corner.
Header Logo Change
In the application, separate header logo changes can be configured to suit the characteristics of the corporate application.
If you want to edit the header logo, follow the steps below.
- Admin Portal > Integration > Select Application > UI > Edit Click the button.
- Header Logo Select custom in the item.
- Text logo and image logo can be selected and set.
- Enter the Korean Redirect URL and the English Redirect URL.
- If the input is completed, check through the right preview whether it was entered correctly.
- Click the Publish button at the lower right corner.
Key Visual Change
In the application, separate key visual changes can be configured to suit the characteristics of the corporate application.
If you want to edit the key visual, follow the steps below.
- Admin Portal > Integration > Application Selection > UI > Edit button, click it.
- Key Visual Select Custom in the item.
- Click to use a single key visual for all languages and language-specific key visuals.
- If the image upload is complete, check through the right preview to see if it was entered correctly.
- Click the Publish button at the lower right.
Redirect
By clicking the application on the list screen, then clicking the edit button in the Rebranding tab, you can configure application-specific rebranding for redirection.
| Category | Description |
|---|---|
| Sign Up | Enter the URL if you want to set a separate sign-up page. |
| Privacy Policy | Enter a separate privacy policy URL in the application. |
| Terms of Service | Enter a separate Terms of Service URL in the I application. |
Application Deletion
From the application list screen, select the application, deactivate it, then return to the list screen and you can delete it from the three‑dot menu. To register again, click the Add button to register.
Identity Provider
This is a menu for registering and managing IdPs that provide authentication services and credentials to SCP SingleID. At this time, SCP SingleID acts as a Service Provider and receives authentication services from the IdP.
Identity Provider List
On the list screen, you can select a registered Identity Provider to edit/delete, sort, search, etc., and you can navigate to a menu screen where you can register a new Identity Provider.
To view the Identity Provider list, you can access the following menu.
- Admin Portal > Integration > Identity Provider
| Category | Description |
|---|---|
| Name | Identity Provider name. |
| Type | Displays the standard protocol registered by the Identity Provider. The Identity Provider type is distinguished by SAML2.0 and OIDC methods. |
| Status | Displays the status of the Identity Provider. It is distinguished as active and inactive. |
| Active button | Only active Identity Providers are displayed in the list. |
| Inactive button | Only inactive Identity Providers are displayed in the list. |
| Search term input field | You can search the Identity Provider list. After entering a search term, click the magnifying glass icon or press Enter to perform the search. Searchable items: name, description |
| Detail button | You can perform a detailed search. Search conditions can be combined with AND. After entering multiple fields, click the Search button, and the search will be performed according to the conditions. Click the Reset button to reset all search fields. |
| Download button | SAML metadata download is available. You can download the SAML metadata files for the internal network and the internet network. |
| Register button | You can register a new application. |
Identity Provider Registration
You can register by clicking Register at the top of the Identity Provider list screen.
To register Identity Provider, follow the steps below.
- Admin Portal > Integration > Identity Provider > Register Click button
- Custom App Integration > Web Application(SAML) or Web Application(OIDC) select > next click the button
- Go to detailed settings
Identity Provider can be registered by entering and setting the information required for integration through a three-step screen as follows.
General
Enter general information for IdP (Identity Provider).
| Category | Description | Required |
|---|---|---|
| Name | Enter the name of the Identity Provider. Since it is identified by name, rules for distinction and management are required. | Required |
| Description | Enter a description of the Identity Provider (business, usage, etc.). | Optional |
| Logo Image | Register a logo that can intuitively identify the Identity Provider. | Optional |
| Login button | Displays IdP as a button/link (Text) etc.
| Required |
SSO
Enter Single Sign On configuration information on the SSO information input screen.
When integrating with Web Application (OIDC)
| Category | Description | Required |
|---|---|---|
| Client ID | Register the Client ID. The Client ID is an ID issued by the authentication server to a registered Client, and because the Client ID itself is information disclosed to the resource owner, it should not be used alone for Client authentication. | Required |
| Client Secret | Register the Client Secret information. The Client Secret is a secret piece of information used for authentication to the target REST service, a unique value known only to the authentication server. | Required |
| Authorization Endpoint URL | The Authorization Endpoint must obtain authorization from the Resource Owner. Enter the Authorization Endpoint URL, which is the URL value used at this time. | Required |
| Token Endpoint URL | Token Endpoint is used by the client and obtains an Access Token via an Authorization Grant or Refresh Token. Enter the Token Endpoint URL, which is the URL value used at this time. | Required |
| Logout URL | Enter the Logout URL, which is the URL value for Return in SLO (Single Logout). | Optional |
| Userinfo Endpoint URL | Provided by the IdP (Identity Provider) and enter the Userinfo Endpoint URL that includes the user profile (username, name, etc.). | Optional |
| IdP Sign-In Key | Set the IdP Sign-In Key value and select the SingleID mapping attribute for the IdP Sign-In Key. | Required |
IdP Sign-In Key Settings There are two ways to handle login in SCP SingleID by receiving the key value that passes the ID.
- How to receive identifier ID value using standard SAML Keyword
- How to create and receive a custom identifier ID
You can map the name obtained by one of the above methods to the User ID, or you can also map it to the CN value. This is a feature that sets how to map authentication information to a value for handling login.
JIT provisioning
Identity Provider’s JIT provisioning feature tab has been added. This feature synchronizes accounts in real time when user changes occur. You can set items when synchronizing accounts in real time.
| Category | Description | Required |
|---|---|---|
| JIT provisioning | JIT provisioning stands for Just-In Provisioning and is an ID and access management feature used to quickly create user accounts when a user logs into the system for the first time.
| Required |
| When there is no SingleID user mapped to the IdP user | Manage actions when the user accesses for the first time.
| Required |
| If there is a SingleID user mapped to the IdP user | If the user exists, update the user information. | Required |
After entering all items and clicking the Complete button, the basic application settings are completed.
Identity Provider Edit
If you click the Identity Provider in the list screen, you can modify the settings.
If you want to modify the Identity Provider, follow the steps below.
- Admin Portal > Integration > Identity Provider Select > Edit Click the button.
- Click the General, SSO, Provisioning, Policy, Assignment tab to edit the items you want to modify.
- Save button을 클릭하세요.
Identity Provider Delete
On the Identity Provider list screen, after selecting an Identity Provider and disabling it, you can return to the list screen and delete it from the three‑dot menu. To register again, click the Add button to register.
Authenticator
Configure by integrating the Authenticator provided by SCP SingleID. By default, password and Email are set to active state.
The Authenticator that is additionally configured and provided is as follows.
- Knox Messenger: OTP can be sent via Knox Messenger.
- PC SSO Agent: SingleID: Provides SSO with Agentless, but uses SSO Agent for multi-browser SSO functionality,
- SingleID Authenticator: It is a SingleID dedicated authentication mobile app that supports biometrics (fingerprint, facial), PIN, mOTP, TOTP.
- SMS: OTP can be sent via mobile SMS.
- Active Directory: Performs authentication with an AD account.
- Passkey: Mobile Passkey, security key, a convenient authentication method that allows easy login with Windows biometric/PIN code.
Authenticator List
We support all authenticators of the six available types.
If you want to check the Authenticator, please check at the following path.
- Admin Portal > Integration > Authenticator
Authenticator Add
When you click Register on the Authenticator list screen, it moves to the next screen and switches to a screen where you can add an Authenticator.
Authenticator를 추가하시려면, 다음의 절차를 따르세요. -> If you want to add an Authenticator, follow the steps below.
- Admin Portal > Integration > Authentictor > Add Click the button.
- each authentication methodto select > Next Click the button.
- Enter the information required for authentication settings.
- Click the Save button.
Authenticator Edit
On the Authenticator list screen, after selecting an Authenticator and clicking edit, it switches to a screen where you can edit.
If you want to modify the Authenticator, follow the steps below.
- Admin Portal > Integration > Authentictor > Edit button click
- Edit each item and click the Edit button to complete the modification.
Authenticator Delete
On the Authenticator list screen, select the Authenticator, deactivate it, then return to the list screen and you can delete it from the three‑dot menu. If you want to register again, click the Add button to register.
MFA Service Provider
MFA Service Provider menu provides a service that enhances user convenience by meeting the security requirements required by companies through multi-factor authentication, applying stronger authentication technologies along with biometric and simple authentication technologies.
MFA Service Provider List
To check the MFA Service Provider list, you can access the following menu.
- Admin Portal > Integration > MFA Service Provider
| Category | Description |
|---|---|
| Name | It is the name of the MFA Service Provider. |
| System Code | Displays system code information. |
| Project Code | Displays the project code information. |
| User Tag | Displays the User Tag. |
| Type | Displays the MFA Service Provider integration method. It is shown in the following three ways.
|
| System Code Input Field | Enter system code information. |
| Project Code Input Field | Enter the project code information. |
| Search input field | You can search the Identity Provider list. After entering a search term, click the magnifying glass icon or press Enter to perform the search.
|
| Detail button | Detailed search is possible. Search conditions can be combined with AND. After entering multiple fields and clicking the ‘Search’ button, the search is performed according to the conditions.
|
| Register button | You can register a new MFA Service Provider. |
MFA Service Provider Registration
To register the MFA Service Provider, follow the steps below.
- Admin Portal > Integration > MFA Service Provider > Register button click
- ADFS Federated Application or Custom Application or Network Equipment select > next button click
MFA Service Provider has three types as follows.
- ADFS Federated Application : Register an ADFS federated application that will be linked with SingleID MFA.
- Custom Application : Register an application that uses the MFA API to be integrated with SingleID MFA.
- Network Equipment : Register network equipment that will be linked with RADIUS-based MFA.
You can register an MFA Service Provider by entering and configuring the information required for MFA Service Provider integration through a three-step screen as follows.
- General
- MFA integration
- [Person in charge](#person in charge)
General
MFA Service Provider Enter general information.
| Category | Description | Required |
|---|---|---|
| Name | Enter the name of the MFA Service Provider. Since it is identified by name, rules for distinction and management are required. | Required |
| Description | Enter description of MFA Service Provider (tasks, usage, etc.). | Optional |
| Logo Image | Register a logo that can intuitively identify the MFA Service Provider. | Optional |
| User Management using User Tag | If you enable the use of User Tag, when a new user is registered from the MFA Service Provider, “#"+User Tag is automatically added after the user’s ID, preventing duplicate ID registration. | Select |
| User Tag | Only one User Tag can be registered per MFA Service Provider.
| Required |
| System Code | Enter system code information. | Optional |
| Project Code | Enter project code information. | Optional |
| Campaign | If only one authentication method is used, a popup page guiding the user to register a personal authentication method is displayed. It becomes active when the selection box is selected. | Select |
MFA integration
Enter MFA integration information.
| Category | Description | Required |
|---|---|---|
| Login | Select the provided Authenticator from the drop-down list. | Required |
| Identity verification at registration | Set the identity verification method that must be performed obligatorily during the registration process.
| Required |
| ADFS Identifier | Please enter the ADFS Identifier URL information. | Required |
| Claim | Enter Claim name.
| Required |
| Secret Key | Secret Key is an encryption key for trusted communication between SingleID and MFA Service Provider.
| Required |
Person in charge
Select and register the person in charge of the newly registered MFA Service Provider.
| Category | Description |
|---|---|
| Add button | You can add a person in charge of the MFA Service Provider. |
| Search | You can find the person in charge by search term (ID, name, email, status). |
| Select (Check Box) | Select the person in charge found in the list. |
| Add | You can add the selected assignee. |
| Complete | Complete assigning the person in charge. |
Click the Complete button to complete the registration.
MFA Service Provider Edit
On the MFA Service Provider list screen, after selecting the Authenticator and clicking edit, it switches to a screen where you can modify.
If you want to modify the MFA Service Provider, follow the steps below.
- Admin Portal > Integration > MFA Service Provider > Edit Click the button.
- Modify each item and click the Edit button to complete the modification.
MFA Service Provider Delete
MFA Service Provider list screen, select the MFA Service Provider, deactivate it, then return to the list screen and you can delete it from the three‑dot menu. To register again, click the Add button to register.