This is the multi-page printable view of this section. Click here to print.

Return to the regular view of this page.

Admin Portal

SingleID provides SSO (Single Sign-On) authentication service and account management (Identity Management) service needed to access various business systems in the company’s on-premise and cloud environments.

All authentication services and account management services of organizations using SingleID, as well as the establishment and configuration of security policies, are managed through the Admin Portal.

Users who can access the Admin Portal to configure and manage the system are called administrators, and through the Admin Portal’s management functions, they can integrate the organization’s business systems without restriction and define security policies to access each business system.

The administrative functions provided by the Admin Portal are as follows.

FunctionDescription
Notification ManagementThrough the user portal, you can register posts to announce to the organization’s users and manage posting periods, etc. If there is urgent information related to system usage, you can post the content on the login screen so that even users who are not logged in can see it.
Application Integration ManagementConnects the organization’s internal business systems or cloud environment business systems. You can configure authentication integration using standard protocols such as SAML, OIDC, or use the SCIM protocol to import information such as accounts and groups into SingleID or export them through SingleID.
Identity Provider Integration ManagementIf an integrated authentication environment is already set up within the organization, you can register the system as an Identity Provider so that you can use applications linked by SingleID without re-authenticating through SingleID. Authentication integration with all Identity Providers that use standard authentication protocols such as SAML and OIDC is possible.
Authenticator ManagementYou can add and manage Authenticators to configure user identity verification or multi-factor authentication. If you add a desktop Authenticator such as PC SSO Agent, you can use multi-browser SSO.
MFA Service Provider Integration ManagementIf you want to increase the security level when accessing business systems while using an already configured in‑organization authentication system, you can link the business system with an MFA Consumer Provider to add only the multi‑factor authentication function to the system. By linking the system with an MFA Consumer Provider, you can configure the authentication environment to perform second‑factor authentication using the Authenticators added to SingleID.
User ManagementYou can view and edit all users registered in the organization, and you can delete users or directly register new users. You can also change a user’s group membership or assign permissions so that the user can use the application.
Group ManagementYou can view and edit all groups registered in the organization, delete groups, or register new groups. You can also change the group’s membership rules or assign permissions so that group members can use the application.
Login Policy ManagementYou can set detailed policies on which authentication methods users can use when logging in with SingleID, and, if necessary, create and manage condition-specific authentication policies for users authenticating in specific environments.
Authentication Policy ManagementAccording to the organization’s security policy, detailed authentication settings can be configured by dividing them into the following four categories: Session Policy, Authenticator Policy, MFA Service Provider Policy, Password Policy
Abnormal behavior detection policy managementSingleID collects and analyzes user behavior information before and after authentication in real time to determine whether there is abnormal authentication behavior, and provides a function that immediately notifies the user of risk when identified as belonging to an abnormal authentication category. Tenant administrators can manage detailed settings of policies for abnormal behavior detection and decide whether each policy is enabled.
Terms and Conditions ManagementUsing the provided templates, register privacy policies, terms of use, and conditions tailored to the organization’s needs, then notify users and obtain their consent.
SMS SettingsSingleID issues OTP via SMS for identity verification and authentication. In SMS Settings, you can configure and set the SMS sent by SingleID.
Table. Admin Portal provided features

If you are using SingleID for the first time, you can set up the basic environment by configuring the functions in the following order.

The supported range and recommended specifications for the SingleID connection environment are as follows.

SupportRecommended
Windows : Windows Desktop 10 and 11 (x86 and x64 CPU Only)
  • Web Browser: Microsoft Edge, Latest public version
Windows : Windows Desktop 10 and 11 (x86 and x64 CPU Only)
  • Web Browser: Microsoft Edge 88.x or higher, Chrome 87.x or higher
Android : 8 and later versions
  • Web Browser: Samsung Internet Latest public version
Android : 8 and later versions
  • Models released in 2018 and beyond among Samsung Galaxy Mobile Products
  • Galaxy S9 ↑
  • Web Browser: Samsung Internet 9.0 ↑
iOS : 16 ,17
  • Web Browser: Safari , Latest public version
iOS : 16 ,17
  • iPhone Xs ↑, Models released in 2018 and beyond among Apple iPhone Products
  • Web Browser: Safari 14.1 ↑
Table. SingleID Connection Environment Support Scope and Recommended Specifications

1 - Dashboard

Notifications are a feature that can deliver and share important alerts related to the use of SingleID to users.

Administrators can register and manage notifications through the notification menu. Administrators select the notification type (normal/urgent) based on the notification content and importance, and when they create a notification, users can receive the notification before login (urgent) or after login (normal/urgent).

The administrator can register and manage notifications to be delivered to users. There are two types of notifications, which are provided as distinguished below.

TypeDescription
GeneralYou can create and deliver a general notice to users. Users can view general notifications in the User Portal > Notifications menu.
UrgentYou can create and deliver urgent notices to users. Users can view urgent alerts in a popup window on the login page.
Table. Notification Type

Notification

List

To check the notification list, access the menu as follows.

  • Admin Portal > Dashboard > Notifications
CategoryDescription
TypeThis is the type of notification.
  • General: If you register a notification as a general announcement, users can view the general notification in the User Portal > Notifications menu.
  • Urgent: If you register a notification as an urgent announcement, users can view the urgent notification via a popup on the login page.
TitleIt is the title of the notification.
PeriodIt is the period for announcing the notification.
RegistrantName of the administrator who registered.
EditorIt is the name of the administrator who edited.
Date ModifiedThis is the date of the last modification.
All buttonBoth regular and urgent notifications can be viewed in the list.
General buttonOnly general notifications can be viewed in the list.
Emergency ButtonOnly emergency alerts can be viewed in the list.
Search term input fieldYou can search the notification list. After entering a search term, click the magnifying glass icon or press Enter to perform the search.
  • Searchable items: Title, Registrant, Modifier
Detail buttonDetailed search is possible. Search conditions can be combined with AND. After entering multiple fields, click the Search button to search according to the conditions.
  • Click the Reset button to reset all search fields.
Registration buttonYou can register a new notification.
Table. List

Notification Registration

If you want to register a notification, follow the steps below.

  1. Admin Portal > Dashboard > Notifications Please click the menu.
  2. Register button, when clicked, you will be taken to the notification registration page.
  3. Check the input items as below and select and enter the details in detail.
  4. Click the Save button.
  5. Check the notifications registered in the list.
CategoryRequired?Description
TypeRequiredNotification type “General”, “Urgent” select
PeriodRequiredSpecify notification posting period “Start Date~End Date”
LanguageRequiredSelect notification language (activates the “Language tab” based on the selected language)
TitleRequiredNotification Title
ContentRequiredWrite notification content
Table. Alarm Registration
Reference

If you exceed the maximum number of characters that can be entered, an error message will be displayed.

All required fields must be entered in all active tabs. Clicking the Cancel button will not save the data and will navigate to the notification list screen.

Notification Edit

If you want to edit the notification, follow the steps below.

  1. Admin Portal > Dashboard > Notifications Please click the menu.
  2. Select the notification that needs editing, and click the Edit button at the bottom of the screen.
  3. After editing the field you want to modify, click the Save button.
  4. Check the edited notification in the list.

Delete Notification

If you want to delete the notification, follow the steps below.

  1. Admin Portal > Dashboard > Notifications Click the menu.
  2. Select the notification that needs to be deleted, and click the Delete button at the top right of the screen.
  3. The notification delete popup appears.
  4. Confirm If you click the button, the notification will be deleted.

Approval Request

When you click the approval request menu, the administrator can view and cancel all users’ approval requests.

The approval request consists of the Approval Request List and Approval Request Queue tabs.

Approval Request List

If you click the approval request list tab, you can view all approval request items.

There are four types of approval request statuses. You can easily filter and view them using the Approval Request, Approve, Reject, Cancel Submission buttons at the top. If you want a detailed search, you can use detailed search in the search bar at the top right.

  • Approval Request: Shows all approval request statuses.
  • Approval: Shows all completed approval statuses.
  • Rejection: Shows approval request items that have been rejected.
  • Submission Cancellation: Shows approval request items where the approval has been cancelled.

The description for the approval request list items is as follows.

NameDescription
Approval SystemRepresents the approval system according to the approval policy. It is possible to check which approval system was used for the request.
Policy > Refer to Approval Policy.
TypeThis is the type of approval request. App Access, Sign Up, Usage Period types are available.
- App Access: This is the type for an application access request.
- Sign Up: This is the type for a sign‑up request during registration
- Usage Period: This is an approval request used when extending the account usage period before it expires.
TitleIt is the approval request title.
RequesterIt is the approval requester.
Recent update dateIt is the update date of the recent approval list.
Request date/timeThis is the initial approval request date and time.
StatusIndicates the status of the approval request. It matches the button at the top.
Table. Approval Request List

Approval request lookup and cancellation

When you click the approval request list, the information of the corresponding approval request appears in a popup. Requests that have not yet been approved can be cancelled by the administrator using the Cancel Request button.

Approval Request Queue

Click the approval request queue tab to view all ongoing approval requests and delete them by selecting all or selecting individually. Through detailed search, if the requester has resigned or the approver is absent, the administrator can arbitrarily cancel (delete) the approval request.

Delete approval request

If you want to delete the approval request, follow the steps below.

  1. check the left selection box of the list (v).
  2. At the top of the list, the Delete button will be activated. Please click the Delete button.
  3. Request Delete Popup appears. Click the Delete button.
  4. The selected approval request in the list has been deleted.

Sign Up

When you click the sign-up menu, the list of sign-up requests appears.

Sign-up Request

When you click the sign-up request tab, the list of sign-up requests appears.

The status of approval requests has four types. You can easily filter and view them using the Approval Request, Approval, Rejection, Submission Cancel buttons at the top. If you want detailed search, you can use detailed search in the search bar at the top right.

  • Approval Request: Shows all approval request statuses.
  • Approval: Shows all completed approval statuses.
  • Rejected: Shows approval request items that have been rejected.
  • Submission Cancellation: Shows approval request items where the approval has been cancelled.
NameDescription
TypeThis is the type of approval request. General, IdP types are available.
- General: When applied through sign‑up on the login page or a separate sign‑up page
- Idp: When sign‑up is requested via an Identity Provider
Approval SystemIndicates the approval system according to the approval policy. It is possible to verify which approval system the request was made through.
Policy > Approval Policy Please refer to.
RequesterIt is the approval requester.
NameIt is the requester’s name.
EmailRequester’s email address.
PhoneIt is the requester’s mobile number.
StatusIndicates the status of the approval request. It matches the button at the top.
Registration DateThis is the sign-up registration date.
Modification DateRecent modification date and time.
Table. Approval Request List

Sign-up Email Invitation

The sign-up email invitation is a method where the administrator sends an invitation email to the desired user via their email address for them to register.

If you want to send an invitation email, follow the steps below.

  1. Dashboard > Sign Up > Sign Up Email Invitation Click the tab.
  2. Click the Send Invitation Email button at the top right.
  3. Invitation Email Sending Popup appears.
  4. Enter the email address to invite in the email field, and click the Add button.
  5. Select the group that will be automatically assigned when a recipient joins the group item. (If not set, the group will be unspecified)
  6. Click the Invite button at the bottom right of the popup.
  7. An invitation email will be sent to the email address you specified.
Reference
Please refer to the Policy > Sign-up Policy menu for detailed sign-up policies.

2 - 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
CategoryDescription
NameThis is the name of the application. It can be entered when creating the application.
TypeClassified by application integration protocols as SAML, OIDC, SCIM.
DisplayThis is a displayed item in the User Portal application list.
  • Display: It is shown to users in the User Portal, allowing them to request access permissions.
  • Blank: It is hidden in the User Portal, making it impossible for users to request directly.
StatusIt is the application status. It is divided into active and inactive.
  • Active: The state where the administrator has completed the settings so that the user can access the application
  • Inactive: The state where the user cannot access the application due to the administrator’s settings
All buttonDisplays all active and inactive applications in the list.
Active buttonOnly active applications are displayed in the list.
Inactive buttonOnly inactive applications are displayed in the list.
Search term input fieldYou can search the application list. After entering a search term, click the magnifying glass icon or press Enter to perform the search.
  • Searchable items: name, description
Detail buttonDetailed 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.
  • Reset button clicking resets all search fields.
Download buttonSAML metadata download is available. You can download the SAML metadata files for the internal network and the internet network.
Register buttonYou can register a new application.
Table. Application List

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).

Reference

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 ProtocolAuthentication linkage, account deployment linkageAuthentication linkageAccount deployment linkage
SAML-
OIDC-
SCIM--
Table. Standard Protocol

To register the application Custom App Integration, follow the steps below.

  1. Admin Portal > Integration > Application > Register Click button
  2. Custom App Integration > Web Application(SAML) orWeb Application(OIDC) or Identity Provisioning(SCIM v2.0) select > Next click the button
  3. 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.

  1. General
  2. SSO
  3. Provisioning
  4. Profile
  5. Policy
  6. Assignment

General

Enter the general application information by referring to the below.

CategoryDescriptionRequired?
NameEnter the application name.Required
DescriptionEnter description of the application.Select
Logo ImageRegister logo. (File upload or URL link)Select
Screen displayDisplayed to the user on the User Portal.Select
Access URLEnter the application access URL.Required
Auto LogoutSet auto logout according to session policy.Select
Automatic RedirectionSet to automatically move to the Service Provider after logout.Select
Logout URLEnter the URL address to navigate to after logout (if not entered, use Access URL)Optional
Table. General Application Information
Reference
Delete Application If you want to delete, select the checkbox ([V]) and then click the Delete button at the top of the list.

SSO

On the SSO information input screen, enter Single Sign On configuration information.

CategoryDescriptionRequired
IssuerEnter the unique identifier value of SP.Required
Single Sign-On URLEnter Full URL for login.Required
Logout URLEnter SLO Return URL.Optional
Logout MethodProvides Back-Channel Logout, Front-Channel Logout (HTTP Redirect Binding), Front-Channel Logout (HTTP POST Binding).Required
Response SigningSAML Response signing setting.Select
Validation On-RequestSetting whether to use Signature Validation.Select
EncryptionEncryption application setting.Select
Application CertificateCertificate registration (PEM format)Required
Attribute to map during SSOSelect SSO connection attribute information and set a unique value.Required
‘Metadata File Import’ buttonProvides SAML metadata file upload functionality. (Identifies ID provider endpoint and certificate)Select
Table. SSO Information
Reference

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.

CategoryDescriptionRequired?
Provisioning ConfigurationIf you want to use account information synchronization, please click the On button. If you select Off, you can skip account synchronization.Required
Base AddressEnter the Base Address (URL) that defines the Endpoint of the target system supporting the SCIM API.Required
AcceptEnter the Accept (e.g., application/json) information, which is the HTTP Accept Header value used in SCIM REQUEST.Required
Content TypeEnter the Content Type (e.g., application/json), which is the HTTP Content Type header value used in SCIM REQUEST.Required
User NameRegisters the User Name used for authentication to the target REST service.Required
PasswordSet the password used for authentication to the target REST service.Required
Bearer TokenRegister the Bearer Token used when calling the API (for authorization).Optional
Client IDRegister 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 SecretRegister 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 IDRegister 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 AddressRegister 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 TypeRegisters 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
ProvisioningSelect one of user or group as the default target for provisioning, and if necessary, you can select both user and group.Select
Inbound Provisioning ScheduleClick On to register periodically (hour, day, month, year) through Intbound Provisioning ScheduleSelect
Outbound Provisioning ScheduleClick On to register the Outbound Provisioning Schedule. Click Off to deploy in real time.Select
Table. Provisioning information input
Reference
If you select Provisioning Configuration to “Off”, the Provisioning stage and profile stage are omitted, and the application registration is set to use only the authentication service, completing the process.

Profile

Enter the setting information for user/group for deployment on the profile information input screen.

CategoryDescriptionRequired
Profile nameEnter the profile name.Required
DescriptionRegister a description for the profile.Optional
AttributeClick Add to select and enter attribute information.Select
Table. Profile Information Input
Notice

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.

CategoryDescriptionRequired?
Login PolicySet 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 ControlThis 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
Table. Policy Settings

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.

  1. If you click the application, you will be taken to the detailed page of that application.
  2. Click the Assign tab and User tab > Assign button
  3. User Assignment When the popup appears, select the user you want to assign, and click the Assign button.
  4. Assignment tab shows the selected user in the list.
Caution

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.
Reference

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.

  1. General
  2. SSO
  3. Provisioning
  4. Profile
  5. Policy
  6. Assignment

General

Enter the general application information by referring to the below.

CategoryDescriptionRequired?
NameEnter the name of the application.Required
DescriptionEnter a description of the application (e.g., tasks, usage, etc.).Optional
Logo ImageRegister a logo that can intuitively identify the application. There are file upload and URL link methods.Optional
Screen displayWhen selected, it is shown to the user in the User Portal.Select
Access URLEnter the application’s Access URL. For the application to access, enter the login page.Required
Auto logoutWhen selected, it will be automatically logged out without re-confirmation according to the session policy.Select
Automatic RedirectionWhen selected, it moves to the Service Provider without displaying the logout completion page.Select
Logout URLEnter the URL address to navigate to when the user logs out. If left blank, it will be set to the Access URL address.Optional
Table. General

SSO

Enter Single Sign On setting information on the SSO information input screen.

CategoryDescriptionRequired
IssuerEnter the Issuer, which is the unique identifier of the SP (Service Provider) and the value verified by the Response Issuer.Required
Single Sign-On URLEnter the Single Sign-On URL, which is the full URL required when logging into the system.Required
Logout URLEnter the Logout URL, which is the URL value for SLO (Single Logout) Return.Optional
Logout MethodThe logout methods for SLO (Single Logout) Return are provided in three ways as follows.
  • Back-Channel Logout: The user logs out safely from the application without interaction.
  • Front-Channel Logout (HTTP Redirect Binding): The user interacts to safely log out from the application using a browser-based logout (HTTP Redirect Binding) method.
  • Front-Channel Logout (HTTP POST Binding): The user interacts to safely log out from the application using a browser-based logout (HTTP POST Binding) method.
Required
Response SigningIf you want to sign the returned SAML Response after the authentication process, use Response Signing.Select
Validation On-RequestCheck to use Signature Validation.Select
EncryptionSelect whether to apply Encryption.Select
Application CertificateIf 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 SSOSelect 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’ buttonThe 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
Table. SSO Information
Guide

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.

CategoryDescriptionRequired
Provisioning ConfigurationClick the ‘On’ button to enable account information synchronization. Selecting ‘Off’ will allow you to SKIP account synchronization.Required
Base AddressEnter the Base Address (URL) that defines the Endpoint of the target system supporting the SCIM API.Required
AcceptEnter the Accept (e.g., application/json) information, which is the HTTP Accept Header value used in SCIM REQUEST.Required
Content TypeEnter the Content Type (e.g., application/json), which is the HTTP Content Type header value used in SCIM REQUEST.Required
User NameRegisters the User Name used for authentication to the target REST service.Required
PasswordSet the password used for authentication to the target REST service.Required
Bearer TokenRegister the Bearer Token used when calling the API (for authorization).Optional
Client IDRegister 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 SecretRegister 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 IDRegister 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 AddressRegister 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 TypeRegisters 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
ProvisioningSelect one of user or group as the default target for provisioning, and if needed you can select both user and group.Select
Inbound Provisioning ScheduleClick On to register periodically (hour, date, month, year) through Intbound Provisioning Schedule.Select
Outbound Provisioning ScheduleClick On to register the Outbound Provisioning Schedule. Click Off to deploy in real time.Select
Table. Provisioning information
Note
If you select Provisioning Configuration as “Off”, the Provisioning stage and profile stage are omitted, and the application registration is set to use only the authentication service and is completed.

Profile

Enter the user/group configuration information for deployment on the profile information input screen.

CategoryDescriptionRequired?
Profile nameEnter the profile name.Required
DescriptionRegister a description for the profile.Required
AttributeClick Add to select and enter attribute information.Required
Table. Profile
Notice

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.

CategoryDescriptionRequired
Login PolicySet 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 ControlThis 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
Table. Policy

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.

  1. When you click the application, you will be taken to the detailed page of that application.
  2. Click the Assign tab and the User tab > Assign button.
  3. User Assignment When the popup appears, select the user you want to assign, and click the Assign button.
  4. Assignment tab shows the selected user in the list.
Caution

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.

Note

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.

  1. Admin Portal > Integration > Select Application > Edit Click the button.
  2. Click the General, SSO, Provisioning, Policy, Assignment, Permission Items, Rebranding tab to edit the items.
  3. Save button을 클릭하세요.
Notice
If you want to deactivate the application, select the application and click the Deactivate button.

Permission Items

The permissions tab provides synchronization integration with the application’s permissions.

If you want to set permissions, follow the steps below.

  1. If you click the application, you will be taken to the detailed page of that application.
  2. Click the Assignment tab and the Permission Items tab > click the Register button.
  3. Permission item When the popup window appears, it is necessary to register the permission item.
  4. 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.
Reference

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.

Guide
Clicking the temporary save at the bottom right allows you to save the settings midway.
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.

  1. Admin Portal > Integration > Select Application > UI > Edit Click the button.
  2. Favicon select custom in the Favicon item.
  3. Favicon image (pencil shape) Click the item, then click the favicon image.
  4. Upload an icon file or enter the icon image URL.
  5. Save button, click it and verify through the preview screen that the upload was successful. 6.Korean page Enter the title in Korean.
  6. English page Enter in English in the title.
  7. If the input is completed, check through the right preview whether it was entered correctly.
  8. Click the Publish button at the lower right corner.
Notice
The recommended size for the favicon image is 256 x 256 px, only ICO files are allowed, and please upload files under 2MB. Favicon images are applied only on PC screens.
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.

  1. Admin Portal > Integration > Select Application > UI > Edit Click the button.
  2. Header Logo Select custom in the item.
  3. Text logo and image logo can be selected and set.
  4. Enter the Korean Redirect URL and the English Redirect URL.
  5. If the input is completed, check through the right preview whether it was entered correctly.
  6. Click the Publish button at the lower right corner.
Notice
The recommended size for the header logo image is 288 x 72 px. Only PNG, JPG, JPEG files are allowed, and please upload files under 1MB. It is possible to set logo images separately for each language.
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.

  1. Admin Portal > Integration > Application Selection > UI > Edit button, click it.
  2. Key Visual Select Custom in the item.
  3. Click to use a single key visual for all languages and language-specific key visuals.
  4. If the image upload is complete, check through the right preview to see if it was entered correctly.
  5. Click the Publish button at the lower right.
Guide
The recommended size for the key visual image is 600 x 612 px. Only PNG, JPG, JPEG files are allowed, and please upload files under 1MB.

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.

Guide
You can save the settings midway by clicking the temporary save at the lower right.
CategoryDescription
Sign UpEnter the URL if you want to set a separate sign-up page.
Privacy PolicyEnter a separate privacy policy URL in the application.
Terms of ServiceEnter a separate Terms of Service URL in the I application.
Table. Redirection
Notice
The default selection outputs the SingleID basic registration page, conditions, and terms.

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
CategoryDescription
NameIdentity Provider name.
TypeDisplays the standard protocol registered by the Identity Provider. The Identity Provider type is distinguished by SAML2.0 and OIDC methods.
StatusDisplays the status of the Identity Provider. It is distinguished as active and inactive.
Active buttonOnly active Identity Providers are displayed in the list.
Inactive buttonOnly inactive Identity Providers are displayed in the list.
Search term input fieldYou 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 buttonYou 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 buttonSAML metadata download is available. You can download the SAML metadata files for the internal network and the internet network.
Register buttonYou can register a new application.
Table. Identity Provider List
Reference
Identity Provider Delete If you want to delete, select the checkbox (V) and then click the Delete button at the top of the list.

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.

  1. Admin Portal > Integration > Identity Provider > Register Click button
  2. Custom App Integration > Web Application(SAML) or Web Application(OIDC) select > next click the button
  3. 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).

CategoryDescriptionRequired
NameEnter the name of the Identity Provider. Since it is identified by name, rules for distinction and management are required.Required
DescriptionEnter a description of the Identity Provider (business, usage, etc.).Optional
Logo ImageRegister a logo that can intuitively identify the Identity Provider.Optional
Login buttonDisplays IdP as a button/link (Text) etc.
  • Logo icon display: Choose whether to display the logo icon on the login button.
  • Button text: Enter the text to display on the login button.
Required
Table. Identity Provider General

SSO

Enter Single Sign On configuration information on the SSO information input screen.

When integrating with Web Application (OIDC)

CategoryDescriptionRequired
Client IDRegister 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 SecretRegister 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 URLThe 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 URLToken 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 URLEnter the Logout URL, which is the URL value for Return in SLO (Single Logout).Optional
Userinfo Endpoint URLProvided by the IdP (Identity Provider) and enter the Userinfo Endpoint URL that includes the user profile (username, name, etc.).Optional
IdP Sign-In KeySet the IdP Sign-In Key value and select the SingleID mapping attribute for the IdP Sign-In Key.Required
Table. Web Application(OIDC) SSO
Guide

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.

CategoryDescriptionRequired
JIT provisioningJIT 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.
  • The feature can be set to On or OFF.
Required
When there is no SingleID user mapped to the IdP userManage actions when the user accesses for the first time.
  • Go to the sign‑up page: create a new account. To prevent ID duplication, set a separate ID suffix for the logged‑in ID.
  • Automatically create a new SingleID user without user invitation: automatically generate an ID.
  • Go to the user registration website: if a separate user sign‑up page exists, navigate to that separate registration page.
Required
If there is a SingleID user mapped to the IdP userIf the user exists, update the user information.Required
Table. JIT provisioning

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.

  1. Admin Portal > Integration > Identity Provider Select > Edit Click the button.
  2. Click the General, SSO, Provisioning, Policy, Assignment tab to edit the items you want to modify.
  3. Save button을 클릭하세요.
Notice
If you want to deactivate the application, select the application and click the Deactivate 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.

  1. Admin Portal > Integration > Authentictor > Add Click the button.
  2. each authentication methodto select > Next Click the button.
  3. Enter the information required for authentication settings.
  4. Click the Save button.
Notice
All nine types of Authenticators, including optimized work environments that a typical IdP service can provide, are already offered and registered/configured, so there are no new Authenticators to add until a new type of Authenticator is needed.
Notice
If you want to disable the Authenticator, select the application and click the Disable 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.

  1. Admin Portal > Integration > Authentictor > Edit button click
  2. 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
CategoryDescription
NameIt is the name of the MFA Service Provider.
System CodeDisplays system code information.
Project CodeDisplays the project code information.
User TagDisplays the User Tag.
TypeDisplays the MFA Service Provider integration method. It is shown in the following three ways.
  • ADFS Plugin
  • MFA API
  • RADIUS
System Code Input FieldEnter system code information.
Project Code Input FieldEnter the project code information.
Search input fieldYou 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, system code, project code
Detail buttonDetailed 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.
  • Reset button: when clicked, all search fields are reset.
Register buttonYou can register a new MFA Service Provider.
Table. MFA Service Provider List

MFA Service Provider Registration

To register the MFA Service Provider, follow the steps below.

  1. Admin Portal > Integration > MFA Service Provider > Register button click
  2. ADFS Federated Application or Custom Application or Network Equipment select > next button click
Notice

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 Service Provider Enter general information.

CategoryDescriptionRequired
NameEnter the name of the MFA Service Provider. Since it is identified by name, rules for distinction and management are required.Required
DescriptionEnter description of MFA Service Provider (tasks, usage, etc.).Optional
Logo ImageRegister a logo that can intuitively identify the MFA Service Provider.Optional
User Management using User TagIf 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 TagOnly one User Tag can be registered per MFA Service Provider.
  • User Tag cannot be modified after registration, and it is a tag attached to the MFA Service Provider and the user.
  • Tenant administrators can define and use User Tags. Users provisioned JIT through the MFA Service Provider have the same User Tag set as a user attribute, allowing you to determine where the user was created.
Required
System CodeEnter system code information.Optional
Project CodeEnter project code information.Optional
CampaignIf 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
Table. MFA Service Provider General

MFA integration

Enter MFA integration information.

CategoryDescriptionRequired
LoginSelect the provided Authenticator from the drop-down list.Required
Identity verification at registrationSet the identity verification method that must be performed obligatorily during the registration process.
  • The user sets first and second Authenticator for identity verification.
  • Delegating authentication to an administrator allows a specific administrator to set authentication on behalf of the user when there is no mobile device or other authentication tool for identity verification.
    ※ It is not recommended to use this except for special circumstances.
Required
ADFS IdentifierPlease enter the ADFS Identifier URL information.Required
ClaimEnter Claim name.
  • A Claim is an authentication method that manages user authentication and permissions through a specific key value, and you can add the necessary data here for use.
  • Defines whether to map to verify if it is the same user. Up to 30 can be registered.
Required
Secret KeySecret Key is an encryption key for trusted communication between SingleID and MFA Service Provider.
  • Issue button to issue it.
Required
Table. MFA Integration
Notice
The person who can verify identity on your behalf can be set in the Person in charge tab.

Person in charge

Select and register the person in charge of the newly registered MFA Service Provider.

CategoryDescription
Add buttonYou can add a person in charge of the MFA Service Provider.
SearchYou 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.
AddYou can add the selected assignee.
CompleteComplete assigning the person in charge.
Table. Person in charge registration

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.

  1. Admin Portal > Integration > MFA Service Provider > Edit Click the button.
  2. 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.

3 - Identity Store

The Identity Store provides a feature to manage users and groups registered in an organization.

There are several cases where users or groups are registered in an organization, such as being provisioned through registered applications or being directly registered by administrators. The Identity Store integrates users and groups registered in various ways, allowing them to be searched and providing various management functions for administrators to configure detailed settings for each user or group. Administrators can manage all users and groups registered in the organization through the Identity Store.

Users

Tenant administrators can use the features provided in the user menu to search and modify all users registered in the organization, delete users, or directly register new users.

Additionally, administrators can change a user’s group membership or assign usage permissions to allow users to use applications.

Users are registered in SingleID in the following ways:

  • Registered through account synchronization (Inbound Provisioning) from an application
  • Registered through Just-In-Time (JIT) provisioning from an Identity Provider
  • Registered from an MFA Service Provider
  • Manually registered by an administrator Administrators can manage registered users in a unified manner using the user menu.

To access the user menu, go to the following menu:

  • Admin Portal > Identity Store > User

User List

You can view and search all users registered in SingleID in a list format.

CategoryDescription
IDThe user’s ID is displayed.
NameThe user’s name is displayed (in the order of last name and first name).
EmailThe user’s email address is displayed.
PhoneThe user’s mobile phone number is displayed.
AdminIndicates whether the user is an administrator of the Admin Portal.
System Mapping IDThe application system mapping ID.
StatusIndicates whether the account is active.
  • Active: The current login-enabled user status.
  • Inactive: The user status that has been intentionally inactivated.
  • Pending: The account synchronization is complete, and the user is in a pending state until they log in.
  • Locked: The account locked due to password errors.
  • Dormant: The account status that has been dormant for a certain period.
Managing EntityIndicates the managing entity of the account. You can see which system the account was automatically registered from or if it was manually registered.
  • SingleID: The account registered directly by the administrator
  • Others: The account synchronized automatically
Registration DateThe initial registration date of the account
Modification DateThe latest update date
Expiration DateThe account expiration date
Dormant User ButtonYou can view dormant users.
Search Input FieldYou can search the user list. Enter a search term and click the magnifying glass icon or press Enter to perform the search.
  • Searchable items: Name, Email, ID
Detail ButtonYou can perform a detailed search. You can search with AND conditions. Enter multiple fields and click the ‘Search’ button to search according to the conditions.
  • Clicking the Reset button initializes all search fields.
Register ButtonYou can register a new MFA Service Provider.
Table. User List
Guide

There are three methods to search for users.

  • Filter by user status
  • Keyword search
  • Advanced search

Filter by User Status

To filter users by status, follow these steps.

  1. Click the button of the group that displays the status you want to filter by. (Only one button can be selected at a time)
  2. After filtering, you can move to another page to view the list of users you want.
  3. After filtering, you can use the keyword search to find the user you want. (However, if you perform an advanced search after filtering, the filter will be removed)
  4. To remove the filter, click the All button.

Keyword Search

To perform a keyword search, follow these steps.

  1. Click on the keyword search input box with your mouse.
  2. Enter the word you want to search for. At this time, a dropdown menu will be displayed below the search input box. If you select one of ID, English Name, Email from the dropdown menu, the search will be executed for the corresponding field, and if you select All, the search will be executed for all ID, English Name, and Email fields.
  3. After entering the search term, press the Enter key or click on the magnifying glass icon with your mouse to execute the search. At this time, the search will be executed for all ID, English Name, and Email fields.
  4. The search results will be displayed in the user list.
  5. If you want to cancel the search results and display the entire list, click the X icon on the right side of the keyword search input box.

Advanced Search To perform an advanced search, follow the procedure below.

  1. Click the Advanced button.
  2. In the advanced search screen, enter the search term in the field you want to search.
  3. In the advanced search screen, you can select the user’s registration date and modification date to limit the search range.
  4. If you enter search terms in multiple fields, the search will be executed with AND conditions.
  5. After entering the search term, press Enter or click the Search button to execute the search.
  6. The search results will be displayed in the user list.
  7. If you want to cancel the search results and display the entire list, click the Reset button in the advanced search screen.

User Registration

The tenant administrator can register users manually on the screen without going through account synchronization.

To register a user, follow the procedure below.

  • Click the Admin Portal > Identity Store > User > Register button

The user can input and register information through a 3-step screen as follows:

  1. Profile
  2. User Group
  3. Summary

Profile

In the profile screen, enter the user’s basic profile information. The fields to be entered are as follows.

ClassificationDescriptionRequired
IDEnter the user’s ID. A value that overlaps with the ID of an already registered user cannot be entered.Required
AdministratorSpecifies whether it is an administrator. Selecting “Allow” gives administrator privileges.Required
Name (Korean name, surname)Enter the Korean name and surname in order.Required
Name (English name, surname)Enter the English name and surname in order. If there is no English name, enter the Korean name and surname again.Required
EmailEnter the email address. This information is used for identity verification, so accurate information must be entered.Required
PhoneEnter the mobile phone number. This information is used for identity verification, so accurate information must be entered.Required
DepartmentEnter the Korean department name and English department name.Optional
OrganizationEnter the Korean organization name and English organization name.Optional
LanguageSpecifies the user’s preferred language. The screen is displayed in the specified language when the user logs in.Required
Time zoneSpecifies the user’s time zone. All times are displayed in the specified time zone when the user logs in.Required
Expiration dateSets the user’s expiration date. The default value is “Not set”.
  • When automatic account deletion is set after the setting date, select the date to be deleted.
Optional
Table. Profile Information

Click the Next button to move to the User Group screen.

User Group

In the User Group screen, specify the group to be registered for the user. The entire group that can be assigned to the user is displayed on the left side of the screen. Select the group to be assigned to the user and click the > button to move to the assigned group.

To cancel group assignment, select the group to be canceled in the assigned group and click the < button. Click the Next button to move to the Summary screen.

Note
The reason for assigning a group to a user is to organically control access in login policies, authentication policies, application access policies, and more.

Summary

  1. On the summary screen, confirm the registered information and register the user.
  2. If you want to modify the entered information, click the Back button to return to the screen you want to modify.
  3. To cancel the registration, click the Cancel button.
  4. Clicking the Complete and Add Registration button registers the user and returns to the profile screen to register a new user.
  5. Clicking the Complete button registers the user and moves to the detailed information screen of the registered user.

User Modification

To modify a user, follow the procedure below.

  1. Click the user you want to modify in Admin Portal > Identity Store > User.
  2. Profile, Group, Application, Multi-factor Authentication (MFA) method, Device, Active Session will be displayed.
  3. Click the Modify button at the bottom and modify the data you want to change.
  4. Click the Save button.

Changing the User’s Status

The status of users managed by SingleID is as follows.

CategoryDescription
ActiveA user who has logged in to SingleID after initial registration, initialized their password, and is using it normally.
InactiveA user whose use has been suspended by the administrator.
PendingA user who has not logged in to SingleID even once after initial registration.
LockedA user who has been locked due to repeated login failures, etc. (The user can unlock themselves through password reset)
Dormant UserAn account status that has been dormant due to no access for a certain period.
Table. User Status

The tenant administrator can change the user’s status according to the user’s current status as follows.

CurrentChangeDescription
ActiveInactiveYou can change the active user to inactive by clicking the inactive button.
InactiveActiveYou can change the inactive user to active by clicking the active button.
PendingNoneA pending user cannot be changed to active or inactive.
LockedActiveA locked user can be changed to active by clicking the password reset button and initializing the password at the same time.
Table. User Status

The button to change the user’s status is exposed as follows in the list and detail screens.

  • When one or more active or inactive users are selected in the list screen
  • When moving to the detail screen of an active or inactive user
Notice
If the tenant administrator attempts to deactivate a user, a confirmation popup will be displayed. To deactivate a user, confirm the user’s information and then click the deactivate button again to change the user’s status from active to inactive. In contrast, when changing a user from inactive to active, no separate confirmation popup is displayed.

Password Reset

The tenant administrator can reset a user’s password. When the tenant administrator resets a user’s password, a guidance email is sent to the user.

Note

The reset password is not displayed to the administrator. Also, the reset password is not directly delivered to the user through the guidance email.

The user must access SingleID directly after receiving the guidance email and use the password reset function to change their password after going through the identity verification process.

To change a user’s password, follow these steps:

  1. Select and click the user to change the password from the user list.
  2. Click the Password Reset button at the top right of the user details screen.
  3. When the confirmation popup is displayed, click the Confirm button.
  4. If the user’s password is reset while it is locked, the lock is released and the status is changed to active.

Group

The tenant administrator can view the groups to which a user belongs and add or delete group memberships.

To manage a user’s group, click the Group tab on the details screen.

ClassificationDescription

| Group Tab | Displays the user’s group management screen. | | All Groups | Displays a list of all groups that can be assigned to the user. | | Assigned Groups | Displays a list of groups that have already been assigned to the user. | | All Groups Search | Searches for groups or group descriptions that can be assigned to the user. The search results are displayed in the list below. To display the entire list after searching, click the X button on the right side of the search input field. | | Assigned Groups Search | Searches for groups or group descriptions that have already been assigned to the user. The search results are displayed in the list below. To display the entire list after searching, click the X button on the right side of the search input field. | | Delete Assigned Groups | Deletes the selected group from the groups assigned to the user. The user is excluded from the members of the deleted group. | | Assign Group | Assigns the selected group to the user. The user becomes a member of the assigned group. |

Group Tab

Delete Group

To delete a group assigned to a user, follow these steps:

  1. Select the group to be deleted from the list of assigned groups. (Check the checkbox to the left of the group name)
  2. Click the < button to delete the assigned group.
Notice
Groups assigned by group rules do not display a checkbox next to the group name. Membership established by rules cannot be manually removed by an administrator.

Assign Group

To assign a new group to a user, follow these steps:

  1. Select the Group to be newly assigned from the list of all groups. (Check the checkbox to the left of the group name)
  2. Click the > button to assign the group.
Notice
When assigning a group, user permissions are automatically granted for the applications assigned to the added group.

Application

The tenant administrator can view the applications that users can use, add or delete applications. To manage a user’s application, click the Application tab on the detailed screen.

ClassificationDescription
Application TabDisplays the application management screen for the user.
Assigned Application ListThe applications assigned to the user are displayed in a list.
Assign ButtonAllows you to assign an application to the user.
Application Tab

Deleting an Application

To delete an application assigned to a user, follow these steps:

Select the application to be deleted from the assigned application list. (Check the checkbox to the left of the application name) Click the Unassign button displayed above the application list. Click the Confirm button in the confirmation popup.

Guide
If you delete an assigned application, it will no longer be displayed in the User Portal > My Apps menu.

Application Assignment

To assign a new application to a user, follow these steps:

  1. Click the Assign button located at the top right of the application list.
  2. In the Application Assignment popup, select the application (check the checkbox to the left of the application name).
  3. Click the Assign button.
  4. If you have assigned all applications, click the Cancel button to close the popup.
Note
Assigned applications can be found in the User Portal > My Apps menu. (If the “Screen Display” option for the assigned application is turned off, it will not be displayed in the user portal.)

Multi-Factor Authentication (MFA) Method Inquiry and Management

The tenant administrator can view the multi-factor authentication method registered by the user and modify or delete some of the registration information.

To manage a user’s multi-factor authentication (MFA) method, click the Multi-Factor Authentication (MFA) Method tab on the detailed screen.

ClassificationDescription
Multi-Factor Authentication (MFA) Method TabDisplays the management screen for the user’s multi-factor authentication (MFA) method.
Multi-Factor Authentication (MFA) Method ListDisplays a list of the user’s registered multi-factor authentication (MFA) methods.
Modify ButtonAllows modification or deletion of the user’s registered multi-factor authentication (MFA) method.
Multi-Factor Authentication (MFA) Method List

Modifying Multi-Factor Authentication (MFA) Method

To modify the MFA method registered by the user, follow the procedure below.

  1. Click the Modify button at the bottom right of the screen.
  2. Click the Registration Information column of the MFA list you want to modify.
  3. After modifying the information, click the Save button at the bottom right of the screen.

Deleting Multi-Factor Authentication (MFA) Method

To delete the MFA method registered by the user, follow the procedure below.

  1. Click the Modify button at the bottom right of the screen.
  2. Click the Delete button to the right of the MFA method you want to delete.
  3. Click the Confirm button in the warning popup.
  4. Click the Save button at the bottom right of the screen.

Viewing User Device Information

The administrator can view the device information added when the user registers the MFA method.

To view the user’s device information, click the Device tab in the detailed screen.

CategoryDescription
Device TabDisplays the user’s device management screen.
Device ListDisplays a list of devices added when the user registers the MFA method.
Device Tab
Notice
Device information can only be viewed and cannot be added, modified, or deleted by the tenant administrator.

Active Sessions

When a user logs in to SingleID, SingleID manages the session information of the logged-in user.

The tenant administrator can view the user’s current active session and manage it to force the session to end and log out the user.

To manage a user’s session, click the Active Sessions tab on the detailed screen.

ClassificationDescription
Active Sessions TabDisplays the user’s session management screen.
Active Sessions ListThe user’s currently active sessions are displayed in a list.
Terminate ButtonForces the user’s active session to terminate.
Active Sessions Tab
Notice
If the user’s active session list is displayed as an empty list, it means that the user is not currently logged in to SingleID.

Session Forced Termination

To forcibly terminate a user’s session, follow these steps:

  1. Click the Terminate button located at the top right of the session you want to terminate.
  2. In the Terminate Confirmation popup, click the Terminate button.
Notice
The terminated user will be forcibly logged out of SingleID and must log in again to use the system. However, the session of the application accessed using SingleID before the session termination will be maintained, and the session of each application will be managed by each application.

Forcible Termination of Multiple Sessions

If you want to terminate multiple sessions simultaneously, follow these steps:

  1. Select the sessions you want to terminate in the list and check the checkbox (V) displayed on the left side of the session information.
  2. Click the Terminate button displayed at the top of the list.
  3. In the Terminate Confirmation popup, click the Terminate button.

User Deletion

The tenant administrator can delete user information from SingleID.

The delete user button is exposed in both the list and detail screens as follows:

  • When one or more users are selected in the list screen
  1. After selecting a user, click the Delete button to display a Confirmation popup on the screen.
  2. To delete a user, confirm the user’s information and enter the user’s ID, then click the Delete button.
  3. When multiple users are selected and the Delete button is clicked, the following Confirmation popup is displayed on the screen.
  4. To delete the selected users, use the <, > buttons to confirm all users’ information, enter Delete All, and then click the Delete button.
    Notice

    You must confirm all user information and enter Delete All to activate the delete button.

    If you have moved to the user details screen

    1. If the administrator wants to delete a user, a confirmation popup will be displayed.
    2. To delete a user, check the user’s information, enter the user’s ID, and click the Delete button.
Note

Deleted user information cannot be recovered.

When user information is deleted, the groups, applications, and multi-factor authentication (MFA) methods assigned to the user are also deleted. Even if you re-register a user with the same ID, the deleted groups, applications, and MFA methods will not be recovered.

Users registered through an application’s inbound provisioning can be re-provisioned from the application even if they are deleted from SingleID.

To completely delete a user, you must delete the user’s information from the original system that manages the user’s information.

Even if a user with the same ID is re-registered after deletion, the deleted groups, applications, and MFA methods will not be automatically recovered.

Group

The administrator can use the functions provided in the Group menu to view and modify all groups registered in the organization, delete groups, or register new groups.

You can also change the group membership rules or assign usage permissions to group members so that they can use applications.

Groups are registered in SingleID in the following ways:

  • Registered through inbound provisioning from an application (Application)
  • Manually registered by the administrator (Create Group) The tenant administrator can manage registered groups in various ways using the group menu.

To access the group menu, move as follows:

  • Admin Portal > Identity Store > Group

Group List

The tenant administrator can view and search all groups registered in the organization in a list format.

ClassificationDescription
Group ListThe group list is displayed.
Keyword SearchSearch by group name and description.
Detailed SearchDetailed options for searching groups are displayed on the screen.
Table. Group List

Create Group

The administrator can manually register a group on the screen without going through inbound provisioning.

  1. To manually register a group, click the Register button on the group list screen.
  2. When you click the Register button, the group registration popup is displayed on the screen.

The fields that must be entered for group registration are as follows:

ClassificationDescriptionRequired
TypeSelect the group type.Required
NameEnter the name of the group. Duplicate values of already registered group names cannot be entered.Required
DescriptionEnter a description of the group.Required
Table. Group List
  1. Complete button is clicked, the group is registered and moves to the detailed information screen of the registered group.

Detailed Information Inquiry and Modification

The administrator can move to the group’s detailed information inquiry screen by clicking the Group in the group list.

If a new group is registered, it will also move to the group’s detailed screen immediately after registration.

At the top of the group detail screen, the group name, description, and management entity information are displayed, and below that, the group information is composed of multiple tabs.

DivisionDescription
TypeThe type of group is displayed.
NameThe name of the group is displayed.
Management EntityThe system that manages the group is displayed. For groups directly registered by the tenant administrator in SingleID, it is displayed as SingleID, and for groups provisioned in through an application, the application name is displayed.
DescriptionThe description of the group is displayed.
Table. Detailed Information Inquiry

The tenant administrator can confirm the detailed information of the registered group through the Group Profile tab.

CategoryDescription
Group ProfileThe group profile will be displayed.
ListA button to return to the list.
EditEdit the profile.
Table. Detailed Information Inquiry

To modify the group’s detailed information, follow the procedure below.

  1. In the group detail screen, select the Profile tab.
  2. Click the Edit button.
  3. Modify the Group Information.

The fields that can be modified are as follows.

CategoryDescriptionRequired
NameEnter the group name. A value that is duplicated with an already registered group name cannot be entered.Required
DescriptionEnter a description of the group.Required
Table. Edit Fields
  1. Click the Save button.
  2. To return to the inquiry state without saving the modified information, click the Cancel button.

Group Membership Rule Management

The administrator can set rules to automatically configure users who meet certain conditions as group members.

When a group rule is set, the tenant administrator does not need to manually manage members, and the group members are automatically configured and added or deleted according to the set condition.

To manage group membership rules, click the Rules tab on the detailed screen.

CategoryDescription
Rules TabThe group rules are displayed.
RulesThe set group rules are displayed. (The default setting for membership policy after creating a group is Off) If the membership policy setting is Off, members are not automatically managed.
ListA button to return to the list.
EditEdits the rules.
Table. Rules Tab

To set a group rule, follow the procedure below.

  1. Select the Rules tab on the group detailed screen.
  2. Click the Edit button.
  3. Click the On button for the membership policy setting.
  4. Set the condition in the WHEN section.
  5. Click the Save button.
  6. To return to the inquiry state without saving the set rule, click the Cancel button.
Notice

When a group membership rule is set, if the administrator changes the user’s detailed information or the user’s detailed information is changed by inbound provisioning, the system automatically searches for users according to the set rule and manages each group member.

Members automatically added according to the group membership rule cannot be manually deleted by the tenant administrator. WHEN area conditions are composed as follows.

ClassificationDescription
Conditional expression operation relationshipIf there is one or more conditional expressions, it defines the operation relationship between conditional expressions. You can choose one of AND or OR, and it is commonly applied to all conditional expressions.
Conditional expression typeSets the type of conditional expression. You can select User Attribute.
Condition itemSets the condition item of the conditional expression. When the type of conditional expression is User Attribute, you can select the user’s attribute from the list.
OperatorSets the operation method of the conditional expression.
Condition valueSets the condition value of the conditional expression.
Add conditional expressionAdds a conditional expression.
Delete conditional expressionDeletes a conditional expression. When there is only one conditional expression, it cannot be deleted.
Table. Rule Tab

The user’s attributes that can be set in the condition item are as follows.

PropertyData TypeDescriptionMandatory
keyStringKeyMandatory
usernameStringIDMandatory
passwordGuardedStringPasswordMandatory
statusStringStatusMandatory
mustChangePasswordBooleanForced password settingMandatory
suspendedBooleanWaiting statusMandatory
creatorStringCreatorOptional
creationDateDateCreation DateOptional
lastModifierStringLast ModifierOptional
lastChangeDateDateLast Change DateOptional
administratorBooleanAdministratorOptional
displayNameStringDisplay NameOptional
cnStringCommon NameOptional
localStringLocale (Email Sending Standard)Optional
userSourceStringUser SourceOptional
syncDateStringLast Sync DateOptional
contractNumberStringContract NumberOptional
contractStartDateStringContract Start DateOptional
contractEndDateStringContract End DateOptional
agreementDateStringAgreement DateOptional
accountStartDateStringAccount Start DateOptional
accountEndDateStringAccount End DateOptional
partnerOrganizationCodeStringPartner Organization CodeOptional
approvalUserStringApproval User IDOptional
formattedNameStringKorean Display NameOptional
familyNameStringKorean Last NameOptional
givenNameStringKorean First NameOptional
enFormattedNameStringEnglish Display NameOptional
enFamilyNameStringEnglish Last NameOptional
enGivenNameStringEnglish First NameOptional
adDomainStringAD DomainOptional
nickNameStringNicknameOptional
employeeNumberStringEmployee NumberOptional
epIdStringEP IDOptional
emailStringEmail AddressOptional
phoneNumberWorkStringPhone NumberOptional
mobileStringPhone NumberOptional
titleStringTitle NameOptional
executiveYnStringExecutive StatusOptional
timeZoneStringTime ZoneOptional
accountLockedBooleanAccount Forced LockOptional
accountAutoLockedBooleanAccount Auto LockOptional
accountDisabledBooleanAccount DisabledOptional
accountSuspendedBooleanDormant AccountOptional
accountSuspendedTimeDateDormant Processing TimeOptional
lastLoginTimeDateLast Login TimeOptional
accountStateStringAccount StatusOptional
Table. Condition Attributes

The operators that can be set in the operator are as follows.

OperatorDescription
EqualsSearches for users whose condition item value matches the condition value.
Not EqualsSearches for users whose condition item value does not match the condition value.
Starts withSearches for users whose condition item value starts with the condition value string.
Ends withSearches for users whose condition item value ends with the condition value string.
ContainsSearches for users whose condition item value contains the condition value string.
Table. Operator List

Group Member Management

Tenant administrators can manually specify members of a group or delete users from group members.

To manage group members, click the Members tab on the detail screen.

NameDescription
Members TabDisplays the group member management screen.
Member ListDisplays group members in a list format.
Filter Button GroupFilters group members by status and displays the list.
Keyword SearchSearches for group members by entering keywords.
Advanced SearchSearches for group members by entering detailed search conditions.
Add ButtonAdds members to the group.
Table. Member Tab

There are three ways to search for members within the group tab.

  • Member status filter
  • Keyword search
  • Advanced search
Notice

Member Status Classification

  • Active: A user who has logged in to SingleID after initial registration, initialized their password, and is currently using it normally
  • Inactive: A user whose use has been suspended by an administrator
  • Pending: A user who has not logged in to SingleID even once after initial registration
  • Locked: A user who has been locked out due to repeated login failures, etc. (in a state where the user can unlock themselves through password reset)

Member Status Filter

To filter members by status, follow these steps:

  1. Click the button for the status of the member you want to filter (Active, Inactive, Pending, Locked button)
  2. You can check the list of members in the filtered state by moving to another page
  3. You can search for the desired member using keyword search in the filtered state (However, if you perform a detailed search in the filtered state, the filter will be removed)
  4. To remove the filter, click the All button

Keyword Search

To perform a keyword search, follow these steps:

  1. Click on the keyword search input box with your mouse
  2. Enter the word you want to search for. At this time, a dropdown menu will be displayed below the search input box. If you select one of the “ID”, “English Name”, or “Email” displayed in the dropdown menu, the search will be executed for the corresponding field, and if you select “All”, the search will be executed for all ID, English Name, and Email fields
  3. After entering the search term, press the Enter key or click on the magnifying glass icon with your mouse to execute the search. At this time, the search will be executed for all ID, English Name, and Email fields
  4. The search results will be displayed in the member list
  5. If you want to cancel the search results and display the entire list, click the X icon on the right side of the keyword search input box

Advanced Search

To perform an advanced search, follow these steps:

  1. Click the Advanced button
  2. Enter the search term in the field you want to search for on the advanced search screen
  3. On the advanced search screen, you can limit the search range by selecting the member’s registration date
  4. If you enter search terms in multiple fields, the search will be executed with an “AND” condition
  5. Enter the search term and press the Enter key or click the Search button to execute the search.
  6. The search results are displayed in the member list.
  7. If you want to cancel the search results and display the entire list, click the Reset button on the detailed search screen.

Member Deletion

To delete a member from a group, follow these steps.

  1. Select one or more members to delete from the member list. (Check the checkbox to the left of the member ID)
  2. Click the Delete button displayed at the top of the list.
  3. Click the Confirm button in the warning popup.
Guide
Deleting a member from a group does not delete the member’s user information. The deleted member will lose the application usage rights assigned through the group.

Member Addition

To add a member to a group, follow these steps.

  1. Click the Add button at the top right of the member list.
  2. In the member addition popup, select one or more users to add as members. (Check the checkbox to the left of the user ID)
  3. Click the Add button.
  4. If you have added all the desired users as members, click the Cancel button in the popup to close the member addition popup.
Guide
Added members will immediately receive application usage permissions assigned through the group.

Application Management

The tenant administrator can view the applications assigned to a group and add or delete applications.

To manage a group’s applications, click the Group tab on the detail screen.

NameDescription
Application TabDisplays the application management screen for the group.
Assigned Application ListThe applications assigned to the group are displayed in a list.
Assign ButtonAllows you to add and assign applications to the group.
Table. Application Management

Application Deletion

To delete an application assigned to a group, follow these steps.

  1. Select the application to be deleted from the list of assigned applications. (Check the checkbox to the left of the application name)
  2. Click the Unassign button displayed above the application list.
  3. Click the Confirm button in the confirmation popup.
Notice
If an assigned application is deleted, it will no longer be displayed in the User Portal > My Apps menu for group members.

Application Assignment

To assign a new application to a group, follow the procedure below.

  1. Click the Assign button displayed at the top right of the application list.
  2. In the Application Assignment popup, select the application. (Check the checkbox to the left of the application name)
  3. Click the Assign button.
  4. If you have assigned all applications, click the Cancel button to close the Application Assignment popup.
Notice
Assigned applications can be found in the User Portal > My Apps menu for group members. (If the Screen Display option for the assigned application is turned off, it will not be displayed in the user portal)

Group Deletion

Tenant administrators can delete groups from SingleID.

The group deletion button is exposed as follows in the list and detail screens.

  • When one or more groups are selected in the list screen
    1. After selecting the group, click the Delete button to display the following Confirmation Popup on the screen.
    2. To delete the group, confirm the group information and enter the group name, then click the Delete button.
    3. If you select multiple groups and click the Delete button, the following Confirmation Popup will be displayed on the screen.
    4. To delete the selected groups, use the <, > buttons to confirm the information of all groups and enter the phrase Delete All, then click the Delete button.
Notice

You must confirm the information of all groups and enter the phrase Delete All to activate the Delete button.

  • Moved to the group detail screen

    1. If the tenant administrator wants to delete a group, a confirmation popup will be displayed as follows.
    2. To delete a group, check the group information, enter the group name, and click the Delete button.
Note
  • The information of the deleted group cannot be recovered again.

  • When the group information is deleted, the group members and application information assigned to the group are also deleted, and even if the group is registered again with the same name, the member or application information is not recovered.

    • Groups registered through the application’s inbound provisioning can be reprovisioned from the application even if they are deleted from SingleID.
    • To completely delete a group, it must be deleted from the ledger system that manages the group information.
    • Even if the group is registered again with the same name after deletion, the deleted members or application information are not automatically recovered.

4 - Policy

When logging in to SingleID or logging in to an application registered with SingleID, various settings such as login method, authentication session, and password must be set according to the organization’s security policy.

SingleID provides a policy management feature that allows for detailed settings for login and authentication information.
If you have purchased the anomaly detection feature (ADM), you can set it to analyze the user’s login behavior when logging in and alert the user to potential security threats when an unusual authentication is detected.

The policy features provided by SingleID are as follows:

  • Login policy
  • Authentication policy
  • Anomaly detection policy

Using SingleID’s policy feature, you can specify a detailed login method according to who, when, and under what environment logs in to which application, creating a secure authentication environment that meets the organization’s security requirements.

Login Policy

The administrator can set a detailed policy on which authentication means can be used to authenticate when a user logs in to SingleID, and can create a conditional authentication policy for users authenticating in a specific environment if necessary.

Login policy can be configured using the following conditions:

  • Which application is logging in?
  • Who logs in?
  • In what environment do they log in?

To access the login policy menu, navigate as follows:

  • Admin Portal > Policies > Login Policy

Basic Login Policy

The Admin Portal has two default policies created as follows.

  • Admin Portal Policy: Policy to control Admin Portal access rights
  • Default Policy: Basic access control policy for users

The Admin Portal Policy is a login policy applied when logging in to the Admin Portal, and the Default Policy is a login policy applied when logging in to the user portal.

After integrating an application with SingleID, if no separate login policy is assigned, the Default Policy is automatically assigned as the basic login policy.

Notice
The above two basic policies cannot be deactivated or deleted.

Registering a Login Policy

The login policy sets the login policy for administrators and users. You can set login policies based on access environment, application, and situation.

The login policy can be registered through a 4-step screen as follows:

  1. General
  2. Assignment
  3. Initial Redirection
  4. Rules

General

In the general screen, enter the name and description of the login policy.

The fields to be entered are as follows.

NameDescriptionRequired
NameEnter the name of the login policy.Required
DescriptionEnter the description of the login policy.Required
Table. General

Click the Next button to move to the assignment screen.

Assignment

In the assignment screen, specify the application to which the login policy will be applied.

NameDescription
FilterFilters applications by status.
Keyword SearchSearches by application name and description.
Detailed SearchDisplays detailed search options for applications on the screen.
Assign ButtonDisplays the application assignment popup on the screen.
Assigned Application ListThe assigned applications are displayed in a list format. The list starts empty.
Table. Assignment
  1. Click the Assign button to display the application assignment popup on the screen.
  2. Application Assignment popup, select one or more applications to assign to the login policy and click the Assign button.
  3. If all applications have been assigned, click the Cancel button to close the Application Assignment popup.

Initial Redirection

The Initial Redirection screen specifies the user’s login screen entry method and login method

  • Redirected to SingleID’s Sign-in page (login page)

  • Redirected to the external IdP


The explanations for the two methods are as follows:

  • If Redirected to SingleID’s Sign-in page is selected, the SingleID login page will be displayed to the user attempting to log in.
  • If Redirected to the external IdP is selected, the login page of the selected Identity Provider will be displayed to the user attempting to log in.
  • After selecting Redirected to the external IdP, you must select and specify the Identity Provider from the selection list.
  • If Redirected to SingleID’s Sign-in page is selected, you can optionally display a button at the bottom of the SingleID login screen that allows the user to log in through an Identity Provider.
  • AND see the following external IdP buttons on the Sign-In page, you can set up the login screen to display by selecting one or more Identity Providers registered with SingleID in the text input box below and clicking the mouse.
Notice
For settings on registering an Identity Provider or displaying a registered Identity Provider on the login screen, refer to Identity Provider Registration.

Rules

On the Rules screen, you can modify or add login rules and set the priority between login rules.

NameDescription
Rule ListThe login rules are displayed on the screen in a list format. The Default Rule is displayed by default, and the Default Rule cannot be deleted.
Keyword SearchSearches by the name or description of the login rule.
Register ButtonRegisters a new login rule.
Complete ButtonRegisters the login policy.
Table. Rule

Default Rule Setting

The login rule list on the rule screen displays the Default Rule by default.

The Default Rule cannot be deleted and can only be modified. Additionally, when one or more login rules are added, the priority cannot be set. (It is always the lowest priority.)

To modify the Default Rule, follow these steps:

  1. Click on the Default Rule in the rule list.
  2. The WHEN condition of the Default Rule cannot be modified.
  3. The THEN result of the Default Rule can be modified.

NameDescription
Access Permission SettingSets the access permission.
Mandatory Authentication MethodSets the primary login method. Additional login methods can be displayed on the login screen besides the default login method.
MFA AuthenticationSets additional login to be required after the primary login is successful.
Terms and Conditions for Collecting Consent and TermsSets the terms and conditions to be displayed and consent to be obtained when the user logs in to SingleID for the first time.
Save ButtonSaves the modified login rule.
Table. Default Rule
You can select one of the following two options in the access permission setting:

  • Deny Access
  • Allow Access

If you select Deny Access, all user logins will be denied.

If you select Allow Access in the access permission setting, you can set the user’s login method.

Notice
  • If you selected Redirected to the external IdP as the login method on the Initial Redirection screen, the primary login setting will not be displayed on the screen.

  • Essential authentication methods are performed by the external Identity Provider based on the Initial Redirection settings.

    • To allow users to log in through multi-factor authentication, check the MFA authentication checkbox and select one or more authenticators in the text input box.

    • If you want to set up the terms and conditions agreement for users logging in to SingleID for the first time, check the terms and conditions agreement setting (d) checkbox and select one or more terms or conditions to be displayed on the screen in the text input box.

Add Rule

To add a login rule, follow these steps:

  1. Click the Register button at the top right of the rule list.
  2. Enter the name and description of the rule on the rule registration screen.
  3. Refer to the following to enter the rule items:
NameDescription
NameThe name of the rule.
DescriptionRule description.
User Group AssignmentSelect the user group to which the rule will be applied.
Profile Attribute AssignmentClick the ‘Add’ button in the profile attribute assignment list to add attributes. For attribute descriptions and operator explanations, refer to the help below.
Group SettingsSpecifies the group to which the logging-in user belongs.
User Attribute ListSpecifies the attributes of the logging-in user and the conditions for each attribute.
Add User Attribute ButtonDisplays the “Add Attribute” popup on the screen.
Table. Rule Addition
Access Environment
NameDescription
NetworkSpecifies the IP or network range of the logging-in user. The default value is “IP address anywhere”.
- Desktop
- Mobile
PlatformSpecifies the device information of the logging-in user. The default value is “Any platforms”.
- Desktop
- Mobile
BrowserSpecifies the browser information of the logging-in user. The default value is “Any browsers”.
- Edge
- Chrome
- Safari
OSSpecifies the OS information of the logging-in user. The default value is “Any OS”.
- Windows 10
- Windows 11
- Android
- iOS
AND Anomalies (Abnormal Behavior)Sets the condition for whether an anomaly was detected during login.
Anomaly detection condition setting is only possible for tenants who have purchased the Anomaly Detection Management (ADM) option.
To use the anomaly detection function (ADM), you must select the additional option when signing the SingleID usage contract.
If you want to use the anomaly detection function, you can make an additional purchase on the SCP product purchase page.
After setting all the “WHEN” condition areas, set the login method to be used when a user who meets the conditions logs in.
Table. Access Environment
Guide

The following are the attributes of the user that can be selected.

User Attribute Information

Attribute NameData TypeRequiredDescription
keyStringRequiredKey
usernameStringRequiredID
passwordGuardedStringRequiredPassword
statusStringRequiredStatus
mustChangePasswordBooleanRequiredPassword Forced Setting
suspendedBooleanRequiredWaiting Status
creatorString-Creator
creationDateDate-Creation Date
lastModifierString-Last Modifier
lastChangeDateDate-Last Change Date
administratorBoolean-Administrator
displayNameString-Display Name
cnString-Common Name
localString-Locale (Email Sending Standard)
userSourceString-User Source
syncDateString-Last Sync Date
contractNumberString-Contract Number
contractStartDateString-Contract Start Date
contractEndDateString-Contract End Date
agreementDateString-Mandatory Agreement Date
accountStartDateString-Account Usage Start Date
accountEndDateString-Account Usage End Date
partnerOrganizationCodeString-Partner Company Code
approvalUserString-Approval User ID
formattedNameString-Korean Display Name
familyNameString-Korean Last Name
givenNameString-Korean First Name
enFormattedNameString-English Display Name
enFamilyNameString-English Last Name
enGivenNameString-English Name
adDomainString-AD Domain
nickNameString-Nickname
employeeNumberString-Employee Number
epIdString-EP ID
emailString-Email Address
phoneNumberWorkString-Phone Number
mobileString-Mobile Phone Number
titleString-Title
enTitleString-English Title
titleCodeString-Title Code
entitlementString-Position
departmentString-Department Name
enDepartmentString-English Department Name
departmentCodeString-Department Code
organizationString-Company Name
enOrganizationString-English Company Name
organizationCodeString-Company Code
regionString-Location
userStatusString-Employee Status
userTypeString-Employee Type
securityLevelString-Security Level
preferredLanguageString-Preferred Language
executiveYnString-Executive Status
timeZoneString-Time Zone
accountLockedBoolean-Account Lock
accountAutoLockedBoolean-Account Auto Lock
accountDisabledBoolean-Account Disabled
accountSuspendedBoolean-Dormant Account
accountSuspendedTimeDate-Dormant Account Time
lastLoginTimeDate-Last Login Time
accountStateString-Account State
Table. User Attributes

Operators are as follows.

OperatorDescription
EqualsSearches for users whose attribute value matches the condition value.
Not EqualsSearches for users whose attribute value does not match the condition value.
Starts withSearches for users whose attribute value starts with the condition string.
Ends withSearches for users whose attribute value ends with the condition string.
ContainsSearches for users whose attribute value contains the condition string.
Table. Operators

THEN Settings

THEN result area sets the login method and procedure.

In the access permission setting (a), you can select one of the following two options:

  • Deny Access
  • Allow Access Deny Access is selected, all user logins will be denied. (The default value of access permission setting (a) is Deny Access)

To allow users to log in and set detailed login methods, select Allow Access.

NameDescription
Access Permission SettingSets the access permission.
Primary Login SettingSets the primary login method. In addition to the default login method, additional login methods can be displayed on the login screen.
Additional Login SettingSets to require additional login after the primary login is successful.
Terms and Conditions Agreement SettingSets to display the terms and conditions and request agreement when the user logs in to SingleID for the first time.
PC SSO Agent SettingSets to check if a security program (Endpoint Security) is installed on the user’s PC using the PC SSO Agent.
Save ButtonSaves the modified login rules.
Table. THEN
  1. In the selection list of the primary login setting, select the Authenticator to be used for login.
  2. If you want to allow the user to log in with another Authenticator in addition to the selected primary login method, select the checkbox (V) of And allow another factors below: and select one or more Authenticators in the text input box.
Guide

If Redirected to the external IdP is selected as the login entry method on the Initial Redirection screen, the primary login setting will not be displayed.

The primary login is performed at the external Identity Provider according to the Initial Redirection setting.

  1. To allow users to log in through multi-factor authentication, select the checkbox (V) of the additional login setting and select one or more Authenticators in the text input field.
  2. To set the terms and conditions agreement when the user logs in to SingleID for the first time, select the checkbox of the terms and conditions agreement setting and select one or more terms or conditions to be displayed on the screen in the text input box.
  3. To check if a security program (Endpoint Security) is installed on the user’s PC using the PC SSO Agent, select the checkbox (V) of the PC SSO Agent setting. If this setting is enabled, login will be blocked for users who do not have a security program installed on their PC.

If the PC SSO Agent is not registered, the PC SSO Agent setting item will not be displayed on the screen. While the PC SSO Agent setting is enabled, instead of blocking the login of users who do not have a security program installed on their PC, you can require additional authentication by selecting the checkbox below and selecting one or more Authenticators in the text input box.

Click the Save button to register the login rule and return to the rule list.

Rule Priority Management

If one or more login rules have been added, the administrator can set the priority of the login rules. If a user meets the conditions set for multiple rules, the login method will be applied according to the rule with the higher priority.

To set the priority of the login rules, follow the procedure below.

  1. Drag the area to the left of the rule name in the rule list with the mouse.
  2. The priority of the login rules will be determined based on the position where they are dragged and dropped.
  3. The higher the position in the rule list, the higher the priority.
Note
The Default Policy has the lowest priority and cannot be changed.

Policy Status Change

The status of the login policy managed by SingleID is as follows.

StatusDescription
ActiveLogin policy that is working normally
InactiveLogin policy that has been suspended by the administrator
Table. Policy Status
Administrators can change the status of the login policy according to the current status of the login policy as follows:

Current StatusChangeable StatusDescription
ActiveInactiveYou can change the active login policy to inactive by clicking the Deactivate button.
InactiveActiveYou can change the inactive login policy to active by clicking the Activate button. You can also delete the inactive login policy.
Table. Policy Status
Notice

Two login policies provided by default in SingleID, Admin Portal Policy and Default Policy, cannot be deactivated.

When a login policy is deactivated, the applications assigned to the deactivated login policy will be automatically changed to be assigned to the default policy (Default Policy).

Policy Deactivation

To deactivate an active login policy, follow these steps:

  1. Click the policy you want to deactivate in the policy list to move to the policy details screen.
  2. Click the Deactivate button.
  3. Confirm the login policy information (the number of assigned applications, the number of rules included in the login policy) displayed in the Confirm popup, and then click the Deactivate button.
Notice

When a login policy is deactivated, the applications assigned to the deactivated login policy will be automatically changed to be assigned to the default policy (Default Policy).

Even if the deactivated login policy is changed back to active, the previously assigned applications will not be automatically reassigned.

Policy Activation

To change the login policy from inactive to active, follow these steps:

  1. Click on the policy you want to activate in the policy list to move to the policy details screen.
  2. Click the Activate button to change the status of the login policy to active.
Notice
When activating an inactive login policy, the status will be changed immediately without a separate confirmation popup.

Policy Deletion

The administrator can delete the login policy from SingleID.

To delete a login policy, follow these steps:

  1. Click on the policy you want to delete in the policy list to move to the policy details screen.
  2. If the login policy is activated, click the Deactivate button to deactivate the policy.
  3. Click the Delete button displayed at the top right of the deactivated login policy.
  4. A popup screen will appear to confirm the deletion of the login policy.
  5. To delete the login policy, confirm the policy information, enter the name of the policy you want to delete, and click the Delete button.
Note

Deleted login policies cannot be recovered.

When a login policy is deleted, the rules included in the policy are also deleted. Even if you register a login policy with the same name, the deleted rules or settings will not be recovered.

Access Simulation

As the number of login policies and rules increases, it can be difficult to understand which user is subject to which policy for login methods. SingleID provides an access simulation feature that allows administrators to quickly check the login policies and rules applied to users.

Using the access simulation feature, you can select a user and an application to access, and define the user’s login environment (network, device, browser, OS) to predict in advance what kind of login method the user will experience in different cases.

Additionally, if there are users who are having trouble logging in and need to review their requests, you can use the access simulation feature to quickly check and modify the policies or rules that are causing the problem.

To use the access simulation feature, click the Access Simulation button at the top right of the login policy list screen.

NameDescription
User ID InputEnter the user ID to be simulated.
Network SettingsSpecify the IP of the user to be simulated. The default value is “IP address anywhere”.
Platform SettingsSpecify the device information of the user to be simulated. The default value is “Any platforms”.
Browser SettingsSpecify the browser information of the user to be simulated. The default value is “Any browsers”.
OS SettingsSpecify the OS information of the user to be simulated. The default value is “Any OS”.
Application SelectionSelect the application to be simulated. Click the application selection button to display a popup.
Run Simulation ButtonRun the access simulation.
Simulation ResultsDisplay the access simulation results on the screen. The login policies and rules applied to the specified user are displayed.
List ButtonReturn to the login policy list.
Table. Access Simulation

To run the access simulation, follow these steps:

  1. Enter the ID of the user to be simulated.
  2. Specify the IP of the user to be simulated. You can select Specific IP Address and enter the IP directly. Enter the IP in the format 123.123.123.123.
  3. Specify the device information of the user to be simulated. You can select Platform and choose a device from the selection list.
  4. Specifies the browser information of the user to be simulated. After selecting Browser, you can select a browser from the selection list.
  5. Specifies the OS information of the user to be simulated. After selecting OS, you can select an OS from the selection list.
  6. Click the Application Selection button to select the target application to be simulated.
  7. In the Application Selection popup, click the radio button to the left of the application name to select the application, and then click the Add button.
Note

If you want to reselect the application, click the X button to the right of the selected application name, and then click the Application Selection button again.

  1. Click the Simulation Run button.
  2. The access simulation is executed, and when the execution is finished, the login policy and rules screen are displayed according to the simulation result.

Authentication Policy

The administrator may need to change the detailed settings related to authentication according to the organization’s security policy.

SingleID manages the detailed settings related to authentication in the following four policies:

  • Session policy
  • Authenticator policy
  • MFA Service Provider policy
  • Password policy

To access the authentication policy menu, move as follows:

  • Admin Portal > Policy > Authentication Policy

To modify the authentication policy, click the Modify button at the bottom right of the authentication policy screen, change the settings, and then click the Save button.

Session Policy

To change the session policy, follow the procedure below:

  1. Click the Modify button at the bottom right of the authentication policy screen.
  2. Set the maximum number of sessions that a user can create at the same time in the maximum session limit setting.
  3. The minimum value that can be set is 1, and the maximum value is 100. If set to 1, the user can only log in from one browser at a time and cannot log in from multiple PCs or browsers simultaneously.
  4. In the session priority setting, you can set the priority of the session created by the user. The priority can be one of the following two options:
    • Old session
    • New session

If the maximum session limit is set to 1 and Old session is selected in the maximum session limit setting, when a logged-in user attempts to log in from another PC or browser that is not logged in, the login will be blocked.

Additionally, if the maximum session limit is set to 1 and New session is selected in the maximum session limit setting, when a logged-in user attempts to log in from another PC or browser that is not logged in, the session of the previously logged-in browser will be forcibly expired, and the session of the new PC or browser will be maintained.

In the maximum session time setting, you can set the maximum time to maintain a session.

The maximum session time can be one of the following two options:

  • No time limit
  • Set time limit

If set to No time limit, once a session is created, it will not expire automatically until the user logs out. If set to Set time limit and a time is set, the session will expire when the set time passes, and the user will be automatically logged out. In the maximum idle session time setting, you can set the maximum idle session time.

If the maximum idle session time is set, the session will expire if the user does not make an authentication request within the set time, and the user will be automatically logged out.

To save the changed settings, click the Save button at the bottom right of the authentication policy screen.

To discard the changed settings without saving, click the Cancel button at the bottom right of the authentication policy screen.

NameDescription
Maximum session limit settingSets the maximum number of concurrent sessions for the user.
Session priority settingSets the priority between the old session and the new session when the number of concurrent sessions exceeds the maximum allowed.
Maximum Session Time SettingSets the maximum time to maintain a session after it is created. The session expires when the maximum session time elapses.
Maximum Idle Session Time SettingSets the time when a session expires if a user does not make an authentication request to the server for a certain period after the session is created.
Table. Access Simulation

Authenticator Policy

To change the Authenticator policy, follow the procedure below.

  1. Click the Edit button at the bottom right of the authentication policy screen.
  2. Set each item as follows.
  3. When the settings are complete, click the Save button.
NameDescription
Available Authenticator Settings
(for login policy)
Sets the Authenticators available for authentication.
Registration Authentication MethodSets the primary identity verification method for users when registering an Authenticator.
Additional AuthenticationSets the additional identity verification methods allowed for users when registering an Authenticator, in addition to the primary method.
Account SearchSets the authentication method for ID search.
Password ResetSets the authentication method for password search.
Unlock SettingIf a user fails to authenticate repeatedly using Authenticators, their ID will be locked. This setting allows you to specify a time after which the lock will be automatically released.
Table. Authenticator Policy
Notice
  1. To remove an Authenticator specified in the available Authenticator settings, it must first be removed from all login policy rules.

Note: I’ve translated only the Korean text into English, leaving the rest of the content (including HTML, code, and Hugo shortcodes) unchanged. 2. Configurable Authenticators can be registered in the Authenticator addition menu. Disabled Authenticators cannot be set in the available Authenticator settings.

Notice

If you haven’t purchased the MFA product

  • Available Authenticator settings (for login policy) will not be displayed on this screen.
  • To purchase additional MFA products, please contact us through Support Center > Inquiry.
Notice
  1. If a user fails to log in due to repeated incorrect password entries and is locked out, the lock will not be released even after a certain period of time. The password lock and release method should be set in the Password Policy.

  2. If you reset a user’s password in the user menu, you can release the lock before the lock release waiting time. Please refer to the password reset.

MFA Service Provider Policy

To change the MFA Service Provider policy, follow the procedure below.

  1. Click the Edit button at the bottom right of the authentication policy screen.
  2. Refer to the table below and set each item accordingly.
  3. When the settings are complete, click the Save button.
NameDescription
Available Authenticator settings
(for MFA Service Provider)
Sets the Authenticator that users can use when an authentication request occurs from the MFA Service Provider.
Terms and Conditions optionWhen a user is registered from the MFA Service Provider, it can display the terms and conditions and obtain the user’s consent.
Lock release settingsWhen an authentication request occurs from the MFA Service Provider and a user fails to authenticate repeatedly, the ID will be locked. It can set the time for the locked user to be automatically released after a certain period of time.
Table. MFA Service Provider Policy
Notice
  1. To remove the specified Authenticator from the available Authenticator settings, the Authenticator must be removed from all MFA Service Providers first.

  2. The Authenticators that can be set are registered in the Authenticator addition menu. Disabled Authenticators cannot be set in the available Authenticator settings.

  3. To set up the terms and conditions to be displayed to the user and to request the user’s consent when the user authenticates from the MFA Service Provider for the first time, check the checkbox in the terms and conditions option and select one or more terms or conditions to be displayed on the screen in the text input box.

  4. If a user who authenticates from the MFA Service Provider repeatedly fails to authenticate, the user’s ID will be locked. To automatically unlock the lock after a certain period of time, set the lock release waiting time in the lock release settings.

Password Policy

To change the password policy, follow the procedure below.

  1. Click the Edit button at the bottom right of the authentication policy screen.
  2. Refer to the table below and set each item accordingly.
  3. When the settings are complete, click the Save button.
NameDescription
Password HistoryYou can set it to prevent the reuse of previously used passwords. Specify the number of recently used passwords to prevent reuse.
The user will not be able to use the password used in the past as many times as set above.
Password ExpirationSpecify the password validity period. After the validity period has passed, you must change your password to log in.
It can be set from 1 day to 365 days.
Password LockThe user’s ID will be locked when the password is repeatedly entered incorrectly. Specify the number of repeated input failures.
  • Automatic lock release after the set time (minutes) (1-1,440): The account that exceeds the set failure count will be locked for the set time (minutes). Enter the automatic lock release time (minutes).
  • Automatic lock release after password reset
Pattern and ComplexitySet the minimum length, minimum characters, numbers, etc. of the password.
Minimum Character SettingSpecify the minimum length of the password.
Minimum Alphabet SettingSpecify the minimum number of alphabets to be included in the password.
Minimum Number SettingSpecify the minimum number of numbers to be included in the password.
Minimum special character settingSpecifies the minimum number of special characters to be included in the password.
Maximum character settingSpecifies the maximum length of the password.
Allow using user ID as passwordSets whether to allow the user’s ID to be included in the password.
Table. Password policy
Notice
A user locked out due to repeated password input failure must reset their password themselves to be unlocked. To change the status of a user locked out due to repeated password input failure, refer to Changing User Status.

Membership registration policy

To allow user membership registration, you must activate the membership registration policy, which allows registration of users other than those provisioned from the personnel system or IdP. It provides features to register, create, modify, and delete accounts through account synchronization, as well as invite users through the login screen or email.

To activate and use the membership registration policy, follow these steps:

  1. Admin Portal > Policy > Membership registration policy.
  2. Activate Allow user membership registration.
  3. After activation, the Policy tab and User invitation tab will appear.
  4. Refer to the explanations of the Policy tab and User invitation tab below and set the policy.
  5. Once the settings are complete, click the Save button.

Policy

You can set general membership registration policies.

NameDescription
Display membership registration link on login screenDisplays the membership registration link on the SingleID login screen.
  • Display SingleID membership registration screen as a link: Select when using the SingleID membership registration screen as default
  • Display external membership registration screen as a link: Select when having a separate membership registration page
Terms and conditions optionSelects the terms and conditions agreement option during membership registration. During membership registration, you can apply terms and conditions separately.
Allow membership registration invitationWhen activated, you can invite users by email. You can set it so that only invited users can join, without a separate membership registration page. In this case, joining through the SingleID membership registration link is not possible.
Registration Input FormSets the user attributes to be input when signing up. Can be added as required.
ID Duplication Prevention SettingIf activated, a suffix is added to the ID to prevent duplication.
This setting is to prevent cases where the ID of an existing auto-provisioned account is the same.
Since there are many cases where the ID value is the same, setting is recommended. When signing up, the PostFix value is added to the end of the ID.
Maximum Usage PeriodThe maximum usage period is set after signing up. Can be set from 1 to 2000 days.
Approval when Signing upWhen the sign-up approval setting is activated, the registered approval policy can be loaded and set.
Table. Policy Tab

Approval Policy

The administrator can select the approval system and set the policy according to the type, such as sign-up policy and app access policy, with various approval lines. Various approval policies can be applied flexibly whenever the security policy changes.

Approval is possible by dividing it into self-approval system function and Knox Portal approval system. If you need to link with another approval system, please request it through 1:1 inquiry.

To check the approval policy, follow the path below.

  • Admin Portal > Policy > Approval Policy

Approval Policy List

The administrator can select the approval system and set the policy according to the type, such as sign-up policy and app access policy, with various approval lines. Various approval policies can be applied flexibly whenever the security policy changes.

NameDescription
IDAutomatically generated ID when creating an approval policy.
Approval SystemDivided into SingleID and Knox Portal. If you need to register another approval system, please request it through 1:1 inquiry.
TypeDivided into app access and sign-up.
StatusApproval policy status. Unavailable means you need to change the approver and notifier.
Approval UseDivided into in use and not in use. Details button click to view the applications using the approval policy.
Table. Approval Policy List

Approval Policy Registration

Register button, you can set the approval system, type, approver, notification method, and approval period.

NameDescription
Approval System2 options are available.
  • SingleID : Self-approval, available through the user portal
  • Knox Portal : Samsung Knox Portal approval system, available for approval
Type2 options are available.
  • App Access : Application access permission application selection
  • Membership : Membership registration application selection
ApproverSelect and register the approver and notifier.
Notification MethodSelect the notification method when an approval request is received by the approver and notifier.
Table. Approval Policy Registration

Anomaly Detection Policy

SingleID collects and analyzes user behavior information in real-time before and after authentication, determining whether the authentication is abnormal. If it is identified as an abnormal authentication category, it immediately notifies the user of the risk.

To access the anomaly detection policy menu, follow these steps:

  • Admin Portal > Policy > Anomaly Detection Policy
Notice
A detailed description of the anomaly detection policy menu is provided separately to ADM purchasing customers. If you have not purchased the anomaly detection feature as an option, you will not be able to view the policy management menu in the Admin Portal. If you want to use the anomaly detection feature, please contact us through 1:1 inquiry or sales representative.

5 - Terms and Conditions

The company using SingleID can manage the Personal Information Processing Policy and Terms of Use, etc. according to the situation and characteristics of each company.

The organization can write a personal information processing policy according to the requirements and notify the user or show the terms of use or terms and conditions to the user using SingleID before use and obtain consent.

Through the Terms and Conditions menu, you can notify users of the Personal Information Processing Policy, Terms of Use, and Terms and Conditions, and obtain consent.

SingleID provides a basic template to make it easy to write terms and conditions.

To access the Terms and Conditions menu, move as follows.

  • Tenant Admin Portal > Rebranding > Terms and Conditions

The functions provided by the Terms and Conditions menu are as follows.

  • Terms and Conditions Attribute Setting
  • Terms and Conditions Version Management
  • Terms and Conditions Publication

Terms and Conditions List

The tenant administrator can view the terms and conditions in a list format.

The basic template provided by SingleID is as follows.

Terms Type Template

  • Privacy
  • Terms of Use
  • Collection and Use of Personal Information
  • Marketing

Conditions Type Template

  • Are you over age 14?

Cookie Type Template

  • Cookie

By clicking on the terms and conditions to be modified in the list, you can move to the detailed screen of the terms and conditions.

NameDescription
TypeThe type is displayed in the form of an icon.
NameThe name is displayed.
DescriptionThe description is displayed.
Type SettingThe type can be changed.
NameThe name can be modified.
Mandatory SettingThe mandatory setting can be set.
Email Notification SettingWhether to set an email notification when the terms and conditions are changed.
DescriptionThe description can be modified.
Registration Date and RegistrarThe registration date and registrar are displayed.
Last Modified DateThe last modified date and last modifier are displayed.
List ButtonA button to return to the list.
Modify ButtonModifies the terms and conditions.
Table. Terms and Conditions List
  1. In the detailed screen of the terms and conditions, select the General Settings tab.
  2. Click the Modify button.
  3. You can modify the Title.
  4. You can modify the Mandatory setting. The available options are as follows.
    • Mandatory: When this term or condition is posted to the user, if the user does not agree, the use will be restricted so that the user cannot log in further.
    • Optional: The agreement is up to the user’s choice, and even if the user does not agree to the terms and conditions, there is no restriction on logging in.
    • Reference: The agreement is not checked.
  5. You can modify the description of the terms and conditions. The description is for reference by the administrator and is not displayed to the user.
  6. After modifying all settings, click the Save button.

If you want to return to the inquiry state without saving the modified information, click the Cancel button.

Terms and Conditions Version Management

The tenant administrator can view and manage the version list of terms and conditions. The default version of terms and conditions is v1.0.0, and it is registered by default for each template when the tenant is created. To check the version list, click the Version History tab in the detailed screen of the terms and conditions.

Version History

The version history can be checked by clicking the Version item at the top of the personal information processing policy and terms of use.

By clicking List, you can check the history of previously published versions. Once a version is published, it cannot be modified.

Version Addition

By clicking the Add button on the Version History tab, you can create a new version of the terms and conditions.

To select version addition, follow the procedure below.

  1. Click the Add button on the Version History tab.
  2. Click the desired Locale to select the writing language.
  3. The selected language represents the region where the terms and conditions will be displayed. The terms and conditions must be written for each language.
  4. Enter the Title and Content for each language.
  5. Click the Save button and click the List button to return to the list.

After completing the writing, review the written content.

Republishing

The newly written version is published by setting the republishing scheduled date.

To publish a new version, follow the procedure below.

  1. Click the Republishing Scheduled Date button on the Version History tab.
  2. Set the Version.
  3. Set the Republishing Date.
  4. Set the Republishing Modification. If activated, the modified terms and conditions will be republished, and the user may need to agree based on the General Settings > Mandatory setting.
  5. Enter a simple reason for the modification.
  6. Click the Publishing Settings button to complete the settings.
Note
Before the republishing scheduled date, the title and content of the terms and conditions can be modified. After republishing, modification is not possible for version management. On the Version History tab, clicking the Delete button on the version history list cancels the republishing.

6 - Open Source licence

The open source licenses used in the SingleID solution are as follows: Please refer to the details below.

SingleID_MobileApp_Client-APK

The following sets forth attribution notices for third party software that may be contained in portions of this product. If you have any questions, please contact <global.cs@samsung.com.>

LicenseOpen Source ComponentLicense Text
Jdom LicenseJDOM(http://www.jdom.org/)JDOM License
Copyright (C) 2000-2004 Jason Hunter & Brett McLaughlin. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice, this list of conditions, and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions, and the disclaimer that follows these conditions in the documentation and/or other materials provided with the distribution.
3. The name “JDOM” must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact {request_AT_jdom_DOT_org}.
4. Products derived from this software may not be called “JDOM”, nor may “JDOM” appear in their name, without prior written permission from the JDOM Project Management {request_AT_jdom_DOT_org}.

In addition, we request (but do not require) that you include in the end-user documentation provided with the redistribution and/or in the software itself an acknowledgment equivalent to the following: “This product includes software developed by the JDOM Project (http://www.jdom.org/)." Alternatively, the acknowledgment may be graphical using the logos available at http://www.jdom.org/images/logos.

THIS SOFTWARE IS PROVIDED “AS IS” AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE JDOM AUTHORS OR THE PROJECT CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
MIT LicenseXamarin.Android.Support.VersionedParcelable (http://www.nuget.org/packages/Xamarin.Android .Support.VersionedParcelable) , Animal Sniffer Annotations (http://mojo.codehaus.org/animal-sniffer/ animal-sniffer-annotations) , Checker Qual (http://checkerframework.org) , Xamarin.Android.Support.SwipeRefreshLayout (http://www.nuget.org/packages/Xamarin.Android .Support.SwipeRefreshLayout) , chai (https://www.npmjs.org/package/chai) , The Legion of the Bouncy Castle (http://www.bouncycastle.org/index.html) , SLF4J API Module(http://www.slf4j.org) , jsrsasign(https://www.npmjs.org/package/jsrsasign) ,Checker Qual(http://checkerframework.org) , , jsrsasign (https://www.npmjs.org/package/jsrsasign) , Mocha(https://www.npmjs.org/package/mocha) , Xamarin.Android.Support.ViewPager (http://www.nuget.org/packages/Xamarin. Android.Support.ViewPager) , SLF4J LOG4J-12 Binding (http://www.slf4j.org) , android-gif-drawable (http://github.com/koral--/android-gif-drawable/)
Android - platform - hardware - intel - common – libva (http://developer.android.com/index.html)
The MIT License

Xamarin.Android.Support.VersionedParcelable : Copyright (c) .NET Foundation Contributors

Animal Sniffer Annotations : Copyright (c) 2009 codehaus.org.

Checker Qual : Copyright 2004-present by the Checker Framework developers

Xamarin.Android.Support.SwipeRefreshLayout : Copyright (c) .NET Foundation Contributors

chai : Copyright (c) 2017 Chai.js Assertion Library

The Legion of the Bouncy Castle : Copyright © 2013 Legion of the Bouncy Castle Inc. (ABN 84 166 338 567) All rights reserved.

SLF4J API Module , SLF4J LOG4J-12 Binding : Copyright © 2004-2023 QOS.ch

jsrsasign : Copyright (c) 2010-2021 Kenji Urushima

Checker Qual : Copyright 2004-present by the Checker Framework developers

Mocha: Copyright (c) 2011-2022 OpenJS Foundation and contributors, https://openjsf.org

Xamarin.Android.Support.ViewPager , Android - platform - hardware - intel - common - libva: Copyright (c) .NET Foundation Contributors

android-gif-drawable : Copyright (c) 2013 - present Karol Wrótniak, Droids on Roids LLC

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF License Open Source Component License Text MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
SingleID_MobileApp_Client-APK

SingleID_MobileApp_Client-IOS

The following sets forth attribution notices for third party software that may be contained in portions of This product. If you have any questions, please contact global.cs@samsung.com

LicenseOpen Source ComponentLicense Text
Apache License 2.0Open Computer Vision Library (OpenCV): KA ProgressLabel:Apache License Version 2.0, January 2004

http://www.apache.org/licenses/

TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

1. Definitions.

“License” shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document.

“Licensor” shall mean the copyright owner or entity authorized by the copyright owner that is granting the License.

“Legal Entity” shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, “control” means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.

“You” (or “Your”) shall mean an individual or Legal Entity exercising permissions granted by this License.

“Source” form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files.

“Object” form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types.

“Work” shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below).

“Derivative Works” shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof.

“Contribution” shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, “submitted” means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as “Not a Contribution.”

“Contributor” shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work.

1. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form.

2. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.

4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions:
a. You must give any other recipients of the Work or Derivative Works a copy of this License; and
b. You must cause any modified files to carry prominent notices stating that You changed the files; and
c. You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, rademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and
d. If the Work includes a “NOTICE” text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License.

You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License.

5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions.

6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file.

7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an “AS IS” BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License.

8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages.

9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS

APPENDIX: How to apply the Apache License to your work
To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets “[]” replaced with your own identifying information. (Don’t include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same “printed page” as the copyright notice for easier identification within third-party archives.

Copyright [yyyy] [name of copyright owner] Licensed under the Apache License, Version 2.0 (the “License”); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an “AS IS” BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
Apple MIT LicenseApple Reachability: https://developer.apple.com/library/ios/samplecode/Reachability/Introduction/Intro.htmlDisclaimer: IMPORTANT: This Apple software is supplied to you by Apple Computer, Inc.

(“Apple”) in consideration of your agreement to the following terms, and your use, installation, modification or redistribution of this Apple software constitutes acceptance of these terms. If you do not agree with these terms, please do not use, install, modify or redistribute this Apple software.

In consideration of your agreement to abide by the following terms, and subject to these terms, Apple grants you a personal, non-exclusive license, under Apple’s copyrights in this original Apple software (the “Apple Software”), to use, reproduce, modify and redistribute the Apple Software, with or without modifications, in source and/or binary forms; provided that if you redistribute the Apple Software in its entirety and without modifications, you must retain this notice and the following text and disclaimers in all such redistributions of the Apple Software. Neither the name, trademarks, service marks or logos of Apple Computer, Inc. may be used to endorse or promote products derived from the Apple Software without specific prior written permission from Apple. Except as expressly stated in this notice, no other rights or licenses, express or implied, are granted by Apple herein, including but not limited to any patent rights that may be infringed by your derivative works or by other works in which the Apple Software may be incorporated.

The Apple Software is provided by Apple on an “AS IS” basis. APPLE MAKES NO WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, REGARDING THE APPLE SOFTWARE OR ITS USE AND OPERATION ALONE OR IN COMBINATION WITH YOUR PRODUCTS.

IN NO EVENT SHALL APPLE BE LIABLE FOR ANY SPECIAL, INDIRECT, INCIDENTAL OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) ARISING IN ANY WAY OUT OF THE USE, REPRODUCTION, MODIFICATION AND/OR DISTRIBUTION OF THE APPLE SOFTWARE, HOWEVER CAUSED AND WHETHER UNDER THEORY OF CONTRACT, TORT (INCLUDING NEGLIGENCE), STRICT LIABILITY OR OTHERWISE, EVEN IF APPLE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Brian Gladman AES LicenseGladman AES: http://www.gladman.me.uk/AESBrian Gladman AES License

Copyright (c) 1998-2013, Brian Gladman, Worcester, UK. All rights reserved. The redistribution and use of this software (with or without changes) is allowed without the payment of fees or royalties provided that:
source code distributions include the above copyright notice, this list of conditions and the following disclaimer; binary distributions include the above copyright notice, this list of conditions and the following disclaimer in their documentation.
This software is provided ‘as is’ with no explicit or implied warranties in respect of its operation, including, but not limited to, correctness and fitness for purpose.
BSD 3-clause “New” or “Revised” LicenseTPPropertyAnimation: http://atastypixel.com/blog/key-path-based-property-animation

Sqlcipher: https://cocoapods.org/pods/SQLCipher

ASM All: http://asm.objectweb.org/asm/

Protocol Buffers [BOM]: https://developers.google.com/protocol-buffers/
TPPropertyAnimation: Copyright 2010 A TASTY PIXEL. All rights Reserved

sqlcipher: Copyright (c) 2008-2023, ZETETIC LLC All rights reserved.

ASM All: Copyright (c) 2000-2011 INRIA, France Telecom All rights reserved.

Protocol Buffers [BOM]: Copyright 2008 Google Inc. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
* Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
* Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
* Neither the name of the nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
MIT LicenseSlatherOrg/slather: https://github.com/SlatherOrg/slather

FDKeychain: https://cocoapods.org/pods/FDKeychain

JSONModel: https://cocoapods.org/pods/JSONModel

FLAnimatedImage: https://cocoapods.org/pods/FLAnimatedImage

Ssziparchive: https://cocoapods.org/pods/SSZipArchive
The MIT License

SlatherOrg/slather: Copyright (c) 2014 Mark Larsen All rights reserved

FDKeychain: Copyright (c) 2016 Reid Main All rights reserved

JSONModel: Copyright (c) 2012-2016 Marin Todorov and JSONModel contributors All rights reserved

FLAnimatedImage: Copyright (c) 2014-2016 Flipboard All rights reserved

ssziparchive: Copyright (c) 2013-2021, ZipArchive, https://github.com/ZipArchive All rights reserved

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
OpenSSL Combined LicenseOpenSSL - in C: http://www.openssl.orgLICENSE ISSUES

The OpenSSL toolkit stays under a dual license, i.e. both the conditions of the OpenSSL License and the original SSLeay license apply to the toolkit. See below for the actual license texts. Actually both licenses are BSD-style Open Source licenses. In case of any license issues related to OpenSSL please contact openssl-core@openssl.org.

OpenSSL License —————

Copyright (c) 1998-2008 The OpenSSL Project. All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
3. All advertising materials mentioning features or use of this software must display the following acknowledgment: “This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. (http://www.openssl.org/)"
4. The names “OpenSSL Toolkit” and “OpenSSL Project” must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact openssl-core@openssl.org.
5. Products derived from this software may not be called “OpenSSL” nor may “OpenSSL” appear in their names without prior written permission of the OpenSSL Project.
6. Redistributions of any form whatsoever must retain the following acknowledgment:

“This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)"

THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT “AS IS” AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

This product includes cryptographic software written by Eric Young (eay@cryptsoft.com). This product includes software written by Tim Hudson (tjh@cryptsoft.com).

Original SSLeay License

Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com) All rights reserved.

This package is an SSL implementation written by Eric Young (eay@cryptsoft.com).
The implementation was written so as to conform with Netscapes SSL.

This library is free for commercial and non-commercial use as long as the following conditions are aheared to. The following conditions apply to all code found in this distribution, be it the RC4, RSA, lhash, DES, etc., code; not just the SSL code. The SSL documentation included with this distribution is covered by the same copyright terms except that the holder is Tim Hudson (tjh@cryptsoft.com). Copyright remains Eric Young’s, and as such any Copyright notices in the code are not to be removed. If this package is used in a product, Eric Young should be given attribution as the author of the parts of the library used. This can be in the form of a textual message at program startup or in documentation (online or textual) provided with the package.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
3. All advertising materials mentioning features or use of this software must display the following acknowledgement:

“This product includes cryptographic software written by Eric Young (eay@cryptsoft.com)” The word ‘cryptographic’ can be left out if the rouines from the library being used are not cryptographic related :-).
4. If you include any Windows specific code (or a derivative thereof) from the apps directory (application code) you must include an acknowledgement: “This product includes software written by Tim Hudson (tjh@cryptsoft.com)”

THIS SOFTWARE IS PROVIDED BY ERIC YOUNG “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

The licence and distribution terms for any publically available version or derivative of this code cannot be changed. i.e. this code cannot simply be copied and put under another distribution licence [including the GNU Public Licence.]
zlib LicenseBase64: https://cocoapods.org/pods/Base64nl

minizip: http://tracker.debian.org/pkg/minizip
The zlib/libpng License

Copyright (c)

This software is provided ‘as-is’, without any express or implied warranty. In no event will the authors be held liable for any damages arising from the use of this software.

Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and redistribute it freely, subject to the following restrictions:

1. The origin of this software must not be misrepresented; you must not claim that you wrote the original software. If you use this software in a product, an acknowledgment in the product documentation would be appreciated but is not required.
2. Altered source versions must be plainly marked as such, and must not be misrepresented as being the original software.
3. This notice may not be removed or altered from any source distribution.
SingleID_MobileApp_Client-APK

SingleID_MobileApp_Flutter-UMA

The following sets forth attribution notices for third party software that may be contained in portions of this product. If you have any questions, please contact global.cs@samsung.com

LicenseOpen Source ComponentLicense Text
Apache License 2.0Android Support Library media compat, Converter: Gson, Adapter: RxJava 2, Android Support Library core utils, Android Arch-Runtime, Guava (Google Common Libraries), Android Support AnimatedVectorDrawable, Android Support Library core UI, Android Support Library Custom View - androidx.customview:customview, Android Lifecycle LiveData, OkHttp, Gson, android.support.annotation, Android Support Library Custom View - androidx.swiperefreshlayout:swiperefreshlayout, Android Support Library v4, OkHttp, Android Lifecycle ViewModel, Commons Lang, rxjava, Android Support Library compat, Roboto Fonts, Apache Commons Collections, Android Support Library v4, Android Lifecycle LiveData Core, RxAndroid, joda-time, okio, Apache Commons IO, JetBrains/java-annotations, Android AppCompat Library v7, Android Support Library Collections, Android Support VectorDrawable, Kotlin Stdlib, Android Lifecycle-Common, Android Support Library loader, RetrofitApache License Version 2.0, January 2004

http://www.apache.org/licenses/

TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

1. Definitions.

“License” shall me an the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document.

“Licensor” shall mean the copyright owner or entity authorized by the copyright owner that is granting the License.

“Legal Entity” shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, “control” means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.

“You” (or “Your”) shall mean an individual or Legal Entity exercising permissions granted by this License.

“Source” form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files.

“Object” form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types.

“Work” shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below).

“Derivative Works” shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof.

“Contribution” shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, “submitted” means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as “Not a Contribution.”

“Contributor” shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work.

2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form.

3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.

4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions:

a. You must give any other recipients of the Work or Derivative Works a copy of this License; and
b. You must cause any modified files to carry prominent notices stating that You changed the files; and
c. You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and
d. If the Work includes a “NOTICE” text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License.

You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License.

5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions.

6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file.

7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an “AS IS” BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License.

8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages.

9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability.

END OF TERMS AND CONDITIONS

APPENDIX: How to apply the Apache License to your work

To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets “[]” replaced with your own identifying information. (Don’t include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same “printed page” as the copyright notice for easier identification within third-party archives.

Copyright [yyyy] [name of copyright owner] Licensed under the Apache License, Version 2.0 (the “License”); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an “AS IS” BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
Creative Commons Zero v1.0 Universalreactive-streams: http://www.reactive-streams.org/Creative Commons CC0 1.0 Universal

Creative Commons Legal Code CC0 1.0 Universal

CREATIVE COMMONS CORPORATION IS NOT A LAW FIRM AND DOES NOT PROVIDE LEGAL SERVICES. DISTRIBUTION OF THIS DOCUMENT DOES NOT CREATE AN ATTORNEY-CLIENT RELATIONSHIP. CREATIVE COMMONS PROVIDES THIS INFORMATION ON AN “AS-IS” BASIS. CREATIVE COMMONS MAKES NO WARRANTIES REGARDING THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS PROVIDED HEREUNDER, AND DISCLAIMS LIABILITY FOR DAMAGES RESULTING FROM THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS PROVIDED HEREUNDER.

Statement of Purpose

The laws of most jurisdictions throughout the world automatically confer exclusive Copyright and Related Rights (defined below) upon the creator and subsequent owner(s) (each and all, an “owner”) of an original work of authorship and/or a database (each, a “Work”).

Certain owners wish to permanently relinquish those rights to a Work for the purpose of contributing to a commons of creative, cultural and scientific works (“Commons”) that the public can reliably and without fear of later claims of infringement build upon, modify, incorporate in other works, reuse and redistribute as freely as possible in any form whatsoever and for any purposes, including without limitation commercial purposes. These owners may contribute to the Commons to promote the ideal of a free culture and the further production of creative, cultural and scientific works, or to gain reputation or greater distribution for their Work in part through the use and efforts of others.

For these and/or other purposes and motivations, and without any expectation of additional consideration or compensation, the person associating CC0 with a Work (the “Affirmer”), to the extent that he or she is an owner of Copyright and Related Rights in the Work, voluntarily elects to apply CC0 to the Work and publicly distribute the Work under its terms, with knowledge of his or her Copyright and Related Rights in the Work and the meaning and intended legal effect of CC0 on those rights.

1. Copyright and Related Rights. A Work made available under CC0 may be protected by copyright and related or neighboring rights (“Copyright and Related Rights”). Copyright and Related Rights include, but are not limited to, the following:

i. the right to reproduce, adapt, distribute, perform, display, communicate, and translate a Work;

ii. moral rights retained by the original author(s) and/or performer(s);

iii. publicity and privacy rights pertaining to a person’s image or likeness depicted in a Work;

iv. rights protecting against unfair competition in regards to a Work, subject to the limitations in paragraph 4(a), below;

v. rights protecting the extraction, dissemination, use and reuse of data in a Work;

vi. database rights (such as those arising under Directive 96/9/EC of the European Parliament and of the Council of 11 March 1996 on the legal protection of databases, and under any national implementation thereof, including any amended or successor version of such directive); and

vii. other similar, equivalent or corresponding rights throughout the world based on applicable law or treaty, and any national implementations thereof.

2. Waiver. To the greatest extent permitted by, but not in contravention of, applicable law, Affirmer hereby overtly, fully, permanently, irrevocably and unconditionally waives, abandons, and surrenders all of Affirmer’s Copyright and Related Rights and associated claims and causes of action, whether now known or unknown (including existing as well as future claims and causes of action), in the Work

i. in all territories worldwide,

ii. for the maximum duration provided by applicable law or treaty (including future time extensions),

iii. in any current or future medium and for any number of copies, and

iv. for any purpose whatsoever, including without limitation commercial, advertising or promotional purposes (the “Waiver”).

Affirmer makes the Waiver for the benefit of each member of the public at large and to the detriment of Affirmer’s heirs and successors, fully intending that such Waiver shall not be subject to revocation, rescission, cancellation, termination, or any other legal or equitable action to disrupt the quiet enjoyment of the Work by the public as contemplated by Affirmer’s express Statement of Purpose.

3. Public License Fallback. Should any part of the Waiver for any reason be judged legally invalid or ineffective under applicable law, then the Waiver shall be preserved to the maximum extent permitted taking into account Affirmer’s express Statement of Purpose. In addition, to the extent the Waiver is so judged Affirmer hereby grants to each affected person a royalty-free, non transferable, non sublicensable, non exclusive, irrevocable and unconditional license to exercise Affirmer’s Copyright and Related Rights in the Work

i. in all territories worldwide,

ii. for the maximum duration provided by applicable law or treaty (including future time extensions),

iii. in any current or future medium and for any number of copies, and

iv. for any purpose whatsoever, including without limitation commercial, advertising or promotional purposes (the “License”).

The License shall be deemed effective as of the date CC0 was applied by Affirmer to the Work. Should any part of the License for any reason be judged legally invalid or ineffective under applicable law, such partial invalidity or ineffectiveness shall not invalidate the remainder of the License, and in such case Affirmer hereby affirms that he or she will not i. exercise any of his or her remaining Copyright and Related Rights in the Work or ii. assert any associated claims and causes of action with respect to the Work, in either case contrary to Affirmer’s express Statement of Purpose.

4. Limitations and Disclaimers.

a. No trademark or patent rights held by Affirmer are waived, abandoned, surrendered, licensed or otherwise affected by this document.

b. Affirmer offers the Work as-is and makes no representations or warranties of any kind concerning the Work, express, implied, statutory or otherwise, including without limitation warranties of title, merchantability, fitness for a particular purpose, non infringement, or the absence of latent or other defects, accuracy, or the present or absence of errors, whether or not discoverable, all to the greatest extent permissible under applicable law.

c. Affirmer disclaims responsibility for clearing rights of other persons that may apply to the Work or any use thereof, including without limitation any person’s Copyright and Related Rights in the Work. Further,

Affirmer disclaims responsibility for obtaining any necessary consents, permissions or other rights required for any use of the Work. Affirmer understands and acknowledges that Creative Commons is not a party to this document and has no duty or obligation with respect to this CC0 or use of the Work.
ISC Licensegotham-fonts: https://www.npmjs.org/package/gotham-fontsISC License (ISCL)

gotham-fonts : Copyright @ Bogdan Pop

Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.

THE SOFTWARE IS PROVIDED “AS IS” AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
MIT LicenseXamarin.Android.Support.VersionedParcelable: http://www.nuget.org/packages/Xamarin.Android.Support.VersionedParcelable

Xamarin.Android.Support.CoordinaterLayout: http://www.nuget.org/packages/Xamarin.Android.Support.CoordinaterLayout

The Legion of the Bouncy Castle: http://www.bouncycastle.org/index.html

Xamarin.Android.Support.SlidingPaneLayout: http://www.nuget.org/packages/Xamarin.Android.Support.SlidingPaneLayout

XamarinLibrary.Xamarin.Android.Support.Multidex: https://www.nuget.org/packages/XamarinLibrary.Xamarin.Android.Support.Multidex

Xamarin.Android.Support.Interpolator: http://www.nuget.org/packages/Xamarin.Android.Support.Interpolator

Xamarin.Android.Support.LocalBroadcastManager: http://www.nuget.org/packages/Xamarin.Android.Support.LocalBroadcastManager

Xamarin.Android.Support.DrawerLayout: http://www.nuget.org/packages/Xamarin.Android.Support.DrawerLayout

@fontsource/Montserrat: https://www.npmjs.org/package/@fontsource/montserrat

Xamarin.Android.Support.DocumentFile: http://www.nuget.org/packages/Xamarin.Android.Support.DocumentFile

Xamarin.Android.Support.Print: http://www.nuget.org/packages/Xamarin.Android.Support.Print

Xamarin.Android.Support.AsyncLayoutInflater: http://www.nuget.org/packages/Xamarin.Android.Support.AsyncLayoutInflater

SLF4J API Module: http://www.slf4j.org

Xamarin.Android.Support.ViewPager: http://www.nuget.org/packages/Xamarin.Android.Support.ViewPager

secure-random: http://github.com/avodonosov/secure-random/

Xamarin.Android.Support.CursorAdapter: http://www.nuget.org/packages/Xamarin.Android.Support.CursorAdapter
The MIT License

Xamarin.Android.Support.VersionedParcelable: Copyright (c) .NET Foundation Contributors All rights reserved.

Xamarin.Android.Support.CoordinaterLayout: Copyright (c) .NET Foundation Contributors All rights reserved.

The Legion of the Bouncy Castle: Copyright (c) 2000-2023 The Legion of the Bouncy Castle Inc. (https://www.bouncycastle.org)

All rights reserved.

Xamarin.Android.Support.SlidingPaneLayout: Copyright (c) .NET Foundation Contributors All rights reserved.

XamarinLibrary.Xamarin.Android.Support.Multidex: Copyright (c) .NET Foundation Contributors All rights reserved.

Xamarin.Android.Support.Interpolator: Copyright (c) .NET Foundation Contributors All rights reserved.

Xamarin.Android.Support.LocalBroadcastManager: Copyright (c) .NET Foundation Contributors All rights reserved.

Xamarin.Android.Support.DrawerLayout: Copyright (c) .NET Foundation Contributors All rights reserved.

@fontsource/Montserrat: Copyright (c) 2023 fontsource All rights reserved.

Xamarin.Android.Support.DocumentFile: Copyright (c) .NET Foundation Contributors All rights reserved.

Xamarin.Android.Support.Print: Copyright (c) .NET Foundation Contributors All rights reserved.

Xamarin.Android.Support.AsyncLayoutInflater: Copyright (c) .NET Foundation Contributors All rights reserved.

SLF4J API Module: Copyright © 2004-2023 QOS.ch All rights reserved.

Xamarin.Android.Support.ViewPager: Copyright (c) .NET Foundation Contributors All rights reserved.

secure-random: Copyright (C) 2011 by Anton Vodonosov (avodonosov@yandex.ru). All rights reserved.

Xamarin.Android.Support.CursorAdapter: Copyright (c) .NET Foundation Contributors All rights reserved.

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
SIL Open Font License 1.1@fontsource/rubik, https://www.npmjs.org/package/@fontsource/rubik

@fontsource/montserrat https://www.npmjs.org/package/@fontsource/montserrat
SIL OPEN FONT LICENSE

Version 1.1 - 26 February 2007

PREAMBLE

The goals of the Open Font License (OFL) are to stimulate worldwide development of collaborative font projects, to support the font creation efforts of academic and linguistic communities, and to provide a free and open framework in which fonts may be shared and improved in partnership with others.

The OFL allows the licensed fonts to be used, studied, modified and redistributed freely as long as they are not sold by themselves. The fonts, including any derivative works, can be bundled, embedded, redistributed and/or sold with any software provided that any reserved names are not used by derivative works. The fonts and derivatives, however, cannot be released under any other type of license. The requirement for fonts to remain under this license does not apply to any document created using the fonts or their derivatives.

DEFINITIONS

“Font Software” refers to the set of files released by the Copyright Holder(s) under this license and clearly marked as such. This may include source files, build scripts and documentation.

“Reserved Font Name” refers to any names specified as such after the copyright statement(s).

“Original Version” refers to the collection of Font Software components as distributed by the Copyright Holder(s).

“Modified Version” refers to any derivative made by adding to, deleting, or substituting — in part or in whole — any of the components of the Original Version, by changing formats or by porting the Font Software to a new environment.

“Author” refers to any designer, engineer, programmer, technical writer or other person who contributed to the Font Software.

PERMISSION & CONDITIONS

Permission is hereby granted, free of charge, to any person obtaining a copy of the Font Software, to use, study, copy, merge, embed, modify, redistribute, and sell modified and unmodified copies of the Font Software, subject to the following conditions:

1. Neither the Font Software nor any of its individual components, in Original or Modified Versions, may be sold by itself.

2. Original or Modified Versions of the Font Software may be bundled, redistributed and/or sold with any software, provided that each copy contains the above copyright notice and this license. These can be included either as stand-alone text files, human-readable headers or in the appropriate machine-readable metadata fields within text or binary files as long as those fields can be easily viewed by the user.

3. No Modified Version of the Font Software may use the Reserved Font Name(s) unless explicit written permission is granted by the corresponding Copyright Holder. This restriction only applies to the primary font name as presented to the users.

4. The name(s) of the Copyright Holder(s) or the Author(s) of the Font Software shall not be used to promote, endorse or advertise any Modified Version, except to acknowledge the contribution(s) of the Copyright Holder(s) and the Author(s) or with their explicit written permission.

5. The Font Software, modified or unmodified, in part or in whole, must be distributed entirely under this license, and must not be distributed under any other license. The requirement for fonts to remain under this license does not apply to any document created using the Font Software.

TERMINATION

This license becomes null and void if any of the above conditions are not met.

DISCLAIMER

THE FONT SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OF COPYRIGHT, PATENT, TRADEMARK, OR OTHER RIGHT. IN NO EVENT SHALL THE COPYRIGHT HOLDER BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, INCLUDING ANY GENERAL, SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF THE USE OR INABILITY TO USE THE FONT SOFTWARE OR FROM OTHER DEALINGS IN THE FONT SOFTWARE.
SingleID_MobileApp_Flutter-UMA

SingleID_SSO-Agent-Windows

The following sets forth attribution notices for third party software that may be contained in portions of this product. If you have any questions, please contact global.cs@samsung.com

LicenseOpen Source ComponentLicense Text
BSD 3-clause “New” or “Revised” LicenseNLog - Advanced .NET Logging http://www.nuget.org/packages/NLogNLog - Advanced .NET Logging:

Copyright (c)2004-2023 Nlog

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

* Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

* Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

* Neither the name of the nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
MIT LicenseJose JWT: http://www.nuget.org/packages/jose-jwt

cassia: http://www.nuget.org/packages/Cassia

Bouncy-Castle: https://www.nuget.org/packages/Bouncy-Castle

Fody: http://www.nuget.org/packages/Fody

Json.NET: http://www.nuget.org/packages/Newtonsoft.Json

Costura.Fody: http://www.nuget.org/packages/Costura.Fody

Opencover: http://www.nuget.org/packages/OpenCover

Fleck2: http://www.nuget.org/packages/Fleck2

chartist-js: http://github.com/gionkunz/chartist-js/
The MIT License

Jose JWT: Copyright (c) 2014-2021 dvsekhvalnov

cassia: Copyright (c) 2008 - 2017 Dan Ports

Bouncy-Castle: Copyright (c) 2000-2023 The Legion of the Bouncy Castle Inc.

Bouncy-Castle: https://www.nuget.org/packages/Bouncy-Castle

Fody: http://www.nuget.org/packages/Fody

Json.NET: http://www.nuget.org/packages/Newtonsoft.Json

Costura.Fody: http://www.nuget.org/packages/Costura.Fody

Opencover: http://www.nuget.org/packages/OpenCover

Fleck2: http://www.nuget.org/packages/Fleck2

chartist-js: http://github.com/gionkunz/chartist-js/

Fody: Copyright (c) Simon Cropp Json.NET: Copyright (c) 2007 James Newton-King

Costura.Fody: Copyright (c) 2012 Simon Cropp and contributors

Opencover: Copyright (c) 2011-2019 Shaun Wilde

Fleck2: Copyright (c) 2013 Peter Sunde

Copyright (c) 2010-2012 Jason Staten

chartist-js: Copyright (c)2013 Gion Kunz gion.kunz@gmail.com

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Mozilla Public License 2.0OpenRPA: https://github.com/open-rpa/openrpa.gitMozilla Public License Version 2.0

1. Definitions

1.1. “Contributor”

means each individual or legal entity that creates, contributes to the creation of, or owns Covered Software.

1.2. “Contributor Version”

means the combination of the Contributions of others (if any) used by a Contributor and that particular Contributor’s Contribution.

1.3. “Contribution”

means Covered Software of a particular Contributor.

1.4. “Covered Software”

means Source Code Form to which the initial Contributor has attached the notice in Exhibit A, the Executable Form of such Source Code Form, and Modifications of such Source Code Form, in each case including portions thereof.

1.5. “Incompatible With Secondary Licenses”

means

a. that the initial Contributor has attached the notice described in Exhibit B to the Covered Software; or

b. that the Covered Software was made available under the terms of version 1.1 or earlier of the License, but not also under the terms of a Secondary License.

1.6. “Executable Form”

means any form of the work other than Source Code Form.

1.7. “Larger Work”

means a work that combines Covered Software with other material, in a separate file or files, that is not Covered Software.

1.8. “License”

means this document.

1.9. “Licensable”

means having the right to grant, to the maximum extent possible, whether at the time of the initial grant or subsequently, any and all of the rights conveyed by this License.

1.10. “Modifications”

means any of the following:

c. any file in Source Code Form that results from an addition to, deletion from, or modification of the contents of Covered Software; or

d. any new file in Source Code Form that contains any Covered Software.

1.11. “Patent Claims” of a Contributor

means any patent claim(s), including without limitation, method, process, and apparatus claims, in any patent Licensable by such Contributor that would be infringed, but for the grant of the License, by the making, using, selling, offering for sale, having made, import, or transfer of either its Contributions or its Contributor Version.

1.12. “Secondary License”

means either the GNU General Public License, Version 2.0, the GNU Lesser General Public License, Version 2.1, the GNU Affero General Public License, Version 3.0, or any later versions of those licenses.

1.13. “Source Code Form”

means the form of the work preferred for making modifications.

1.14. “You” (or “Your”)

means an individual or a legal entity exercising rights under this License. For legal entities, “You” includes any entity that controls, is controlled by, or is under common control with You. For purposes of this definition, “control” means (a) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (b) ownership of more than fifty percent (50%) of the outstanding shares or beneficial ownership of such entity.

2. License Grants and Conditions

2.1. Grants

Each Contributor hereby grants You a world-wide, royalty-free, non-exclusive license:

a. under intellectual property rights (other than patent or trademark) Licensable by such Contributor to use, reproduce, make available, modify, display, perform, distribute, and otherwise exploit its Contributions, either on an unmodified basis, with Modifications, or as part of a Larger Work; and

b. under Patent Claims of such Contributor to make, use, sell, offer for sale, have made, import, and otherwise transfer either its Contributions or its Contributor Version.

2.2. Effective Date

The licenses granted in Section 2.1 with respect to any Contribution become effective for each Contribution on the date the Contributor first distributes such Contribution.

2.3. Limitations on Grant Scope

The licenses granted in this Section 2 are the only rights granted under this License. No additional rights or licenses will be implied from the distribution or licensing of Covered Software under this License. Notwithstanding Section 2.1(b) above, no patent license is granted by a Contributor:

c. for any code that a Contributor has removed from Covered Software; or

d. for infringements caused by: (i) Your and any other third party’s modifications of Covered Software, or (ii) the combination of its Contributions with other software (except as part of its Contributor Version); or

e. under Patent Claims infringed by Covered Software in the absence of its Contributions.

This License does not grant any rights in the trademarks, service marks, or logos of any Contributor (except as may be necessary to comply with the notice requirements in Section 3.4).

2.4. Subsequent Licenses

No Contributor makes additional grants as a result of Your choice to distribute the Covered Software under a subsequent version of this License (see Section 10.2) or under the terms of a Secondary License (if permitted under the terms of Section 3.3).

2.5. Representation

Each Contributor represents that the Contributor believes its Contributions are its original creation(s) or it has sufficient rights to grant the rights to its Contributions conveyed by this License.

2.6. Fair Use

This License is not intended to limit any rights You have under applicable copyright doctrines of fair use, fair dealing, or other equivalents.

2.7. Conditions

Sections 3.1, 3.2, 3.3, and 3.4 are conditions of the licenses granted in Section 2.1.

3. Responsibilities

3.1. Distribution of Source Form

All distribution of Covered Software in Source Code Form, including any Modifications that You create or to which You contribute, must be under the terms of this License. You must inform recipients that the Source Code Form of the Covered Software is governed by the terms of this License, and how they can obtain a copy of this License. You may not attempt to alter or restrict the recipients’ rights in the Source Code Form.

3.2. Distribution of Executable Form

If You distribute Covered Software in Executable Form then:

a. such Covered Software must also be made available in Source Code Form, as described in Section 3.1, and You must inform recipients of the Executable Form how they can obtain a copy of such Source Code Form by reasonable means in a timely manner, at a charge no more than the cost of distribution to the recipient; and

b. You may distribute such Executable Form under the terms of this License, or sublicense it under different terms, provided that the license for the Executable Form does not attempt to limit or alter the recipients’ rights in the Source Code Form under this License.

3.3. Distribution of a Larger Work

You may create and distribute a Larger Work under terms of Your choice, provided that You also comply with the requirements of this License for the Covered Software. If the Larger Work is a combination of Covered Software with a work governed by one or more Secondary Licenses, and the Covered Software is not Incompatible With Secondary Licenses, this License permits You to additionally distribute such Covered Software under the terms of such Secondary License(s), so that the recipient of the Larger Work may, at their option, further distribute the Covered Software under the terms of either this License or such Secondary License(s).

3.4. Notices

You may not remove or alter the substance of any license notices (including copyright notices, patent notices, disclaimers of warranty, or limitations of liability) contained within the Source Code Form of the Covered Software, except that You may alter any license notices to the extent required to remedy known factual inaccuracies.

3.5. Application of Additional Terms

You may choose to offer, and to charge a fee for, warranty, support, indemnity or liability obligations to one or more recipients of Covered Software. However, You may do so only on Your own behalf, and not on behalf of any Contributor. You must make it absolutely clear that any such warranty, support, indemnity, or liability obligation is offered by You alone, and You hereby agree to indemnify every Contributor for any liability incurred by such Contributor as a result of warranty, support, indemnity or liability terms You offer. You may include additional disclaimers of warranty and limitations of liability specific to any jurisdiction.

4. Inability to Comply Due to Statute or Regulation

If it is impossible for You to comply with any of the terms of this License with respect to some or all of the Covered Software due to statute, judicial order, or regulation then You must: (a) comply with the terms of this License to the maximum extent possible; and (b) describe the limitations and the code they affect. Such description must be placed in a text file included with all distributions of the Covered Software under this License. Except to the extent prohibited by statute or regulation, such description must be sufficiently detailed for a recipient of ordinary skill to be able to understand it.

5. Termination

5.1. The rights granted under this License will terminate automatically if You fail to comply with any of its terms. However, if You become compliant, then the rights granted under this License from a particular Contributor are reinstated (a) provisionally, unless and until such Contributor explicitly and finally terminates Your grants, and (b) on an ongoing basis, if such Contributor fails to notify You of the non-compliance by some reasonable means prior to 60 days after You have come back into compliance. Moreover, Your grants from a particular Contributor are reinstated on an ongoing basis if such Contributor notifies You of the non-compliance by some reasonable means, this is the first time You have received notice of non-compliance with this License from such Contributor, and You become compliant prior to 30 days after Your receipt of the notice.

5.2. If You initiate litigation against any entity by asserting a patent infringement claim (excluding declaratory judgment actions, counter-claims, and cross-claims) alleging that a Contributor Version directly or indirectly infringes any patent, then the rights granted to You by any and all Contributors for the Covered Software under Section 2.1 of this License shall terminate.

5.3. In the event of termination under Sections 5.1 or 5.2 above, all end user license agreements (excluding distributors and resellers) which have been validly granted by You or Your distributors under this License prior to termination shall survive termination.

6. Disclaimer of Warranty

Covered Software is provided under this License on an “as is” basis, without warranty of any kind, either expressed, implied, or statutory, including, without limitation, warranties that the Covered Software is free of defects, merchantable, fit for a particular purpose or non-infringing. The entire risk as to the quality and performance of the Covered Software is with You. Should any Covered Software prove defective in any respect, You (not any Contributor) assume the cost of any necessary servicing, repair, or correction. This disclaimer of warranty constitutes an essential part of this License. No use of any Covered Software is authorized under this License except under this disclaimer.

7. Limitation of Liability

Under no circumstances and under no legal theory, whether tort (including negligence), contract, or otherwise, shall any Contributor, or anyone who distributes Covered Software as permitted above, be liable to You for any direct, indirect, special, incidental, or consequential damages of any character including, without limitation, damages for lost profits, loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses, even if such party shall have been informed of the possibility of such damages. This limitation of liability shall not apply to liability for death or personal injury resulting from such party’s negligence to the extent applicable law prohibits such limitation. Some jurisdictions do not allow the exclusion or limitation of incidental or consequential damages, so this exclusion and limitation may not apply to You.

8. Litigation

Any litigation relating to this License may be brought only in the courts of a jurisdiction where the defendant maintains its principal place of business and such litigation shall be governed by laws of that jurisdiction, without reference to its conflict-of-law provisions. Nothing in this Section shall prevent a party’s ability to bring cross-claims or counter-claims.

9. Miscellaneous This License represents the complete agreement concerning the subject matter hereof. If any provision of this License is held to be unenforceable, such provision shall be reformed only to the extent necessary to make it enforceable. Any law or regulation which provides that the language of a contract shall be construed against the drafter shall not be used to construe this License against a Contributor.

10. Versions of the License

10.1. New Versions Mozilla Foundation is the license steward. Except as provided in Section 10.3, no one other than the license steward has the right to modify or publish new versions of this License. Each version will be given a distinguishing version number.

10.2. Effect of New Versions You may distribute the Covered Software under the terms of the version of the License under which You originally received the Covered Software, or under the terms of any subsequent version published by the license steward.

10.3. Modified Versions

If you create software not governed by this License, and you want to create a new license for such software, you may create and use a modified version of this License if you rename the license and remove any references to the name of the license steward (except to note that such modified license differs from this License).

10.4. Distributing Source Code Form that is Incompatible With Secondary Licenses

If You choose to distribute Source Code Form that is Incompatible With Secondary Licenses under the terms of this version of the License, the notice described in Exhibit B of this License must be attached.

Exhibit A - Source Code Form License Notice

This Source Code Form is subject to the terms of the Mozilla Public License, v. 2.0. If a copy of the MPL was not distributed with this file, You can obtain one at http://mozilla.org/MPL/2.0/.

If it is not possible or desirable to put the notice in a particular file, then You may include the notice in a location (such as a LICENSE file in a relevant directory) where a recipient would be likely to look for such a notice.

You may add additional accurate notices of copyright ownership.

Exhibit B - “Incompatible With Secondary Licenses” Notice

This Source Code Form is “Incompatible With Secondary Licenses”, as defined by the Mozilla Public License, v. 2.0.
SingleID_SSO-Agent-Windows

SingleID_ADFS-Adapter

The following sets forth attribution notices for third party software that may be contained in portions of this product. If you have any questions, please contact global.cs@samsung.com

LicenseOpen Source ComponentLicense Text
Apache License 2.0Microsoft.NetFramework.Analyzers, Microsoft.CodeAnalysis.VersionCheckAnalyzer, Microsoft.NetCore.Analyzers, Microsoft.CodeAnalysis.FxCopAnalyzers, Microsoft.CodeQuality.AnalyzersApache License Version 2.0, January 2004

http://www.apache.org/licenses/

TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

1. Definitions.

“License” shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document.

“Licensor” shall mean the copyright owner or entity authorized by the copyright owner that is granting the License.

“Legal Entity” shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, “control” means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.

“You” (or “Your”) shall mean an individual or Legal Entity exercising permissions granted by this License. “Source” form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files.

“Object” form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types.

“Work” shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice License Open Source Software License Text that is included in or attached to the work (an example is provided in the Appendix below).

“Derivative Works” shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof.

“Contribution” shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, “submitted” means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as “Not a Contribution.”

“Contributor” shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work.

2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form.

3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.

4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions:

a. You must give any other recipients of the Work or Derivative Works a copy of this License; and

b. You must cause any modified files to carry prominent notices stating that You changed the files; and

c. You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and

d. If the Work includes a “NOTICE” text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License.

You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License.

You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License.

5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions.

6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file.

7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an “AS IS” BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or License Open Source Software License Text redistributing the Work and assume any risks associated with Your exercise of permissions under this License.

8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages.

9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability.

END OF TERMS AND CONDITIONS

APPENDIX: How to apply the Apache License to your work

To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets “[]” replaced with your own identifying information. (Don’t include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same “printed page” as the copyright notice for easier identification within third-party archives.

Copyright [yyyy] [name of copyright owner] Licensed under the Apache License, Version 2.0 (the “License”); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an “AS IS” BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
Microsoft .NET Library LicenseSystem.Security.Claims http://www.nuget.org/packages/System.Security.ClaimsMICROSOFT SOFTWARE LICENSE TERMS MICROSOFT .NET LIBRARY

These license terms are an agreement between Microsoft Corporation (or based on where you live, one of its affiliates) and you. Please read them. They apply to the software named above, which includes the media on which you received it, if any. The terms also apply to any Microsoft

* updates,

* supplements,

* Internet-based services, and

* support services

for this software, unless other terms accompany those items. If so, those terms apply.

BY USING THE SOFTWARE, YOU ACCEPT THESE TERMS. IF YOU DO NOT ACCEPT THEM, DO NOT USE THE SOFTWARE.

IF YOU COMPLY WITH THESE LICENSE TERMS, YOU HAVE THE PERPETUAL RIGHTS BELOW.

1. INSTALLATION AND USE RIGHTS.

a. Installation and Use. You may install and use any number of copies of the software to design, develop and test your programs. You may modify, copy, distribute or deploy any .js files contained in the software as part of your programs.

b. Third Party Programs. The software may include third party programs that Microsoft, not the third party, licenses to you under this agreement. Notices, if any, for the third party program are included for your information only.

2. ADDITIONAL LICENSING REQUIREMENTS AND/OR USE RIGHTS.

a. DISTRIBUTABLE CODE. In addition to the .js files described above, the software is comprised of Distributable Code. “Distributable Code” is code that you are permitted to distribute in programs you develop if you comply with the terms below.

i. Right to Use and Distribute.

* You may copy and distribute the object code form of the software.

* Third Party Distribution. You may permit distributors of your programs to copy and distribute the Distributable Code as part of those programs.

ii. Distribution Requirements. For any Distributable Code you distribute, you must

* use the Distributable Code in your programs and not as a standalone distribution;

* require distributors and external end users to agree to terms that protect it at least as much as this agreement;

* display your valid copyright notice on your programs; and

* indemnify, defend, and hold harmless Microsoft from any claims, including attorneys’ fees, related to the distribution or use of your programs.

iii. Distribution Restrictions. You may not

* alter any copyright, trademark or patent notice in the Distributable Code;

* use Microsoft’s trademarks in your programs’ names or in a way that suggests your programs come from or are endorsed by Microsoft;

* include Distributable Code in malicious, deceptive or unlawful programs; or

* modify or distribute the source code of any Distributable Code so that any part of it becomes subject to an Excluded License. An Excluded License is one that requires, as a condition of use, modification or distribution, that

* the code be disclosed or distributed in source code form; or

* others have the right to modify it. 3. SCOPE OF LICENSE. The software is licensed, not sold. This agreement only gives you some rights to use the software. Microsoft reserves all other rights. Unless applicable law gives you more rights despite this limitation, you may use the software only as expressly permitted in this agreement. In doing so, you must comply with any technical limitations in the software that only allow you to use it in certain ways. You may not

* work around any technical limitations in the software;

* reverse engineer, decompile or disassemble the software, except and only to the extent that applicable law expressly permits, despite this limitation;

* publish the software for others to copy;

* rent, lease or lend the software; or

* transfer the software or this agreement to any third party.

BACKUP COPY.

You may make one backup copy of the software. You may use it only to reinstall the software.

DOCUMENTATION.

Any person that has valid access to your computer or internal network may copy and use the documentation for your internal, reference purposes.

EXPORT RESTRICTIONS.

The software is subject to United States export laws and regulations. You must comply with all domestic and international export laws and regulations that apply to the software. These laws include restrictions on destinations, end users and end use. For additional information, see www.microsoft.com/exporting SUPPORT SERVICES. Because this software is “as is,” we may not provide support services for it. ENTIRE AGREEMENT. This agreement, and the terms for supplements, updates, Internet-based services and support services that you use, are the entire agreement for the software and support services. APPLICABLE LAW.

a. United States. If you acquired the software in the United States, Washington state law governs the interpretation of this agreement and applies to claims for breach of it, regardless of conflict of laws principles. The laws of the state where you live govern all other claims, including claims under state consumer protection laws, unfair competition laws, and in tort.

b. Outside the United States. If you acquired the software in any other country, the laws of that country apply.

LEGAL EFFECT.

This agreement describes certain legal rights. You may have other rights under the laws of your country. You may also have rights with respect to the party from whom you acquired the software. This agreement does not change your rights under the laws of your country if the laws of your country do not permit it to do so.

DISCLAIMER OF WARRANTY. THE SOFTWARE IS LICENSED “AS-IS.” YOU BEAR THE RISK OF USING IT. MICROSOFT GIVES NO EXPRESS WARRANTIES, GUARANTEES OR CONDITIONS. YOU MAY HAVE ADDITIONAL CONSUMER RIGHTS OR STATUTORY GUARANTEES UNDER YOUR LOCAL LAWS WHICH THIS AGREEMENT CANNOT CHANGE. TO THE EXTENT PERMITTED UNDER YOUR LOCAL LAWS, MICROSOFT EXCLUDES THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT.

FOR AUSTRALIA – YOU HAVE STATUTORY GUARANTEES UNDER THE AUSTRALIAN CONSUMER LAW AND NOTHING IN THESE TERMS IS INTENDED TO AFFECT THOSE RIGHTS.

LIMITATION ON AND EXCLUSION OF REMEDIES AND DAMAGES. YOU CAN RECOVER FROM MICROSOFT AND ITS SUPPLIERS ONLY DIRECT DAMAGES UP TO U.S. $5.00. YOU CANNOT RECOVER ANY OTHER DAMAGES, INCLUDING CONSEQUENTIAL, LOST PROFITS, SPECIAL, INDIRECT OR INCIDENTAL DAMAGES.

This limitation applies to

* anything related to the software, services, content (including code) on third party Internet sites, or third party programs; and claims for breach of contract, breach of warranty, guarantee or condition, strict liability, negligence, or other tort to the extent permitted by applicable law.

It also applies even if Microsoft knew or should have known about the possibility of the damages. The above limitation or exclusion may not apply to you because your country may not allow the exclusion or limitation of incidental, consequential or other damages.

Please note: As this software is distributed in Quebec, Canada, some of the clauses in this agreement are provided below in French.

Remarque : Ce logiciel étant distribué au Québec, Canada, certaines des clauses dans ce contrat sont fournies ci-dessous en français.

EXONÉRATION DE GARANTIE. Le logiciel visé par une licence est offert « tel quel ». Toute utilisation de ce logiciel est à votre seule risque et péril. Microsoft n’accorde aucune autre garantie expresse. Vous pouvez bénéficier de droits additionnels en vertu du droit local sur la protection des consommateurs, que ce contrat ne peut modifier. La ou elles sont permises par le droit locale, les garanties implicites de qualité marchande, d’adéquation à un usage particulier et d’absence de contrefaçon sont exclues.

LIMITATION DES DOMMAGES-INTÉRÊTS ET EXCLUSION DE RESPONSABILITÉ POUR LES DOMMAGES. Vous pouvez obtenir de Microsoft et de ses fournisseurs une indemnisation en cas de dommages directs uniquement à hauteur de 5,00 $ US. Vous ne pouvez prétendre àaucune indemnisation pour les autres dommages, y compris les dommages spéciaux, indirects ou accessoires et pertes de bénéfices.

Cette limitation concerne :

* tout ce qui est relié au logiciel, aux services ou au contenu (y compris le code) figurant sur des sites Internet tiers ou dans des programmes tiers ; et

* les réclamations au titre de violation de contrat ou de garantie, ou au titre de responsabilité stricte, de négligence ou d’une autre faute dans la limite autorisée par la loi en vigueur.

Elle s’applique également, même si Microsoft connaissait ou devrait connaître l’éventualité d’un tel dommage. Si votre pays n’autorise pas l’exclusion ou la limitation de responsabilité pour les dommages indirects, accessoires ou de quelque nature que ce soit, il se peut que la limitation ou l’exclusion ci-dessus ne s’appliquera pas à votre égard.

EFFET JURIDIQUE. Le présent contrat décrit certains droits juridiques. Vous pourriez avoir d’autres droits prévus par les lois de votre pays. Le présent contrat ne modifie pas les droits que vous confèrent les lois de votre pays si celles-ci ne le permettent pas.
MIT LicenseSystem.IdentityModel.Tokens.Jwt, http://www.nuget.org/packages/System.IdentityModel.Tokens.Jwt

Microsoft.IdentityModel.Abstractions, https://www.nuget.org/packages/Microsoft.IdentityModel.Abstractions

System.ValueTuple, http://www.nuget.org/packages/System.ValueTuple

System.Threading.Tasks.Extensions, http://www.nuget.org/packages/System.Threading.Tasks.Extensions

System.Security.AccessControl, http://www.nuget.org/packages/System.Security.AccessControl

System.IO.FileSystem.AccessControl, http://www.nuget.org/packages/System.IO.FileSystem.AccessControl

System.Runtime.CompilerServices.Unsafe, http://www.nuget.org/packages/System.Runtime.CompilerServices.Unsafe

Microsoft.Bcl.AsyncInterfaces, https://www.nuget.org/packages/Microsoft.Bcl.AsyncInterfaces

System.DirectoryServices, http://www.nuget.org/packages/System.DirectoryServices

System.Buffers, http://www.nuget.org/packages/System.Buffers

System.Text.Json, http://www.nuget.org/packages/System.Text.Json

Microsoft.IdentityModel.Tokens, http://www.nuget.org/packages/Microsoft.IdentityModel.Tokens

System.Numerics.Vectors, http://www.nuget.org/packages/System.Numerics.Vectors

Microsoft.IdentityModel.Logging, http://www.nuget.org/packages/Microsoft.IdentityModel.Logging

System.Security.Principal.Windows, http://www.nuget.org/packages/System.Security.Principal.Windows

System.Memory, http://www.nuget.org/packages/System.Memory

System.Text.Encodings.Web, http://www.nuget.org/packages/System.Text.Encodings.Web

azure-activedirectory-identitymodel-extensions-for-dotnet http://www.nuget.org/packages/Microsoft.IdentityModel.JsonWebTokens
The MIT License

azure-activedirectory-identitymodel-extensions-for-dotnet

Copyright (c) Microsoft Corporation. All rights reserved.

Microsoft.Bcl.AsyncInterfaces

Copyright (c) Microsoft Corporation. All rights reserved.

Microsoft.IdentityModel.Abstractions

Copyright (c) Microsoft Corporation. All rights reserved

Microsoft.IdentityModel.Logging

Copyright (c) Microsoft Corporation. All rights reserved

Microsoft.IdentityModel.Tokens

Copyright (c) Microsoft Corporation. All rights reserved

System.Buffers

Copyright (c) Microsoft Corporation. All rights reserved

System.DirectoryServices

Copyright (c) Microsoft Corporation. All rights reserved

System.IdentityModel.Tokens.Jwt

Copyright (c) Microsoft Corporation. All rights reserved

System.IO.FileSystem.AccessControl

Copyright (c) Microsoft Corporation. All rights reserved

System.Memory

Copyright (c) Microsoft Corporation. All rights reserved

System.Numerics.Vectors

Copyright (c) Microsoft Corporation. All rights reserved

System.Runtime.CompilerServices.Unsafe

Copyright (c) Microsoft Corporation. All rights reserved

System.Security.AccessControl

Copyright (c) Microsoft Corporation. All rights reserved

System.Security.Principal.Windows

Copyright (c) Microsoft Corporation. All rights reserved

System.Text.Encodings.Web

Copyright (c) Microsoft Corporation. All rights reserved

System.Text.Json

Copyright (c) Microsoft Corporation. All rights reserved

System.Threading.Tasks.Extensions

Copyright (c) Microsoft Corporation. All rights reserved

System.ValueTuple Copyright (c) Microsoft Corporation. All rights reserved

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
SingleID_ADFS-Adapter