Upload 2 files

okta_dataset_eval.jsonl

@@ -0,0 +1,73 @@
+{"text":"### Human: How to Create group rules in Okta? ### Assistant: You can create a group rule to assign a user to groups or exclude them from a group. You can use basic conditions or the Okta Expression Language to create rules.
+
+If you're evaluating attributes from Workday, Active Directory, or other sources, you first need to map them to Okta user profile attributes.
+
+Create a group rule
+In the Admin Console, go to DirectoryGroups.
+Select the Rules tab, and then click Add Rule.
+Enter a name for the rule.
+For the IF condition, select one of these options:
+Use basic condition: Select options from the drop-down lists to create a rule using string attributes only. Use this method to create simple rules. For example, those from a single attribute or from one or more groups only.
+Use Okta Expression Language (advanced): Select this option to create complex rules with custom expressions.
+
+You can create rules using the following:
+
+One or more attributes
+One or more groups
+Combinations of attributes and groups
+See About Okta Expression Language.
+
+In Then Assign to, enter a single group or multiple groups to which the user should be assigned if the rule condition is met.
+
+IMPORTANT: You can assign a user to maximum 100 groups.
+
+In Except The following users, enter the names of any users you want to exclude from the rule.
+
+IMPORTANT:
+
+You can exclude maximum 100 users from a rule.
+If you manually remove a rule-managed user from a group, that user automatically gets added to Except The following users for that rule.
+Click Save.
+After you create and save a rule, it’s inactive by default. Once you activate it, the rule gets applied to your entire org. The new rule then runs on a user as their profile gets updated through import, direct updating, or other changes. The rule doesn't move users in a Pending or Inactive state."},
+{"text":"### Human: How to Add a social login (IdP) in Okta? ### Assistant: In the Admin Console, go to SecurityIdentity Providers.
+Click Add identity provider, and then select a social login (IdP).
+Follow the setup information for the IdP from Add an external Identity Provider.
+"},
+{"text":"### Human: How to Configure an app sign-on policy in Okta? ### Assistant : App sign-on policies allow or restrict access to applications. To set up an app sign-on policy:
+
+In the Admin Console, go to ApplicationsApplications.
+Click the desired app.
+Click the Sign On tab.
+Scroll down to the Sign On Policy section.
+Create a rule:
+Click Add Rule.
+Enter a name in the Rule Name field.
+Decide to whom the rule applies by selecting an option under the People section.
+Users assigned this app: Specify the users who are assigned this specific app.
+The following groups and users: Assign the rule to groups or specific users who have been assigned the app.
+To exclude specific groups and users from the policy rule, select Exclude the following users and groups from this rule. Then specify groups and users.
+Configure Conditions:
+Location: Specify the location to which you want the policy to apply. Available options are Anywhere, In Zone, or Not in Zone.
+
+If you select In Zone, enter the name of a zone. You configure zone names in Security > Network. See Network zones and Dynamic zones.
+
+Client: Choose the conditions that you want to trigger the actions you configure in the Access section:
+
+(Microsoft Office 365 apps only.) In If the user's client is any of these, select the client types that you want to trigger the actions you configure in the Actions section (Web browser or Modern Auth client). For details, see the Client section in Office 365 Client Access Policies.
+In And the user's platform is any of these, select the mobile and/or desktop platforms that you want to trigger the actions you configure in the Access section.
+Device Trust: Specify the trust status of the device that you want to trigger the actions you configure in the Access section. The Trusted and Not Trusted options are only selectable if Device Trust is configured in Security > Device Trust. Okta Device Trust determines devices to be trusted based on the presence of a trust signal (MDM enrollment; certificate; support for Universal Links).
+
+Configure the Actions that you want to enforce based on the conditions you specified in the Conditions section:
+Access:
+
+In the setting When all the conditions above are met, sign on to this application is select either Allowed or Denied.
+(SAML apps only) Select Prompt for re-authentication and specify how frequently you want users to be prompted to re-authenticate. The time period that you specify begins from the moment the user last authenticated into Okta.
+Note:
+
+A 10-second grace period applies after a user authenticates with their password. During this grace period, users aren't prompted for their password again if Every sign-in attempt is selected under Re-authentication frequency.
+This feature is available for all SAML-configured apps.
+Because SWA apps don't support re-authentication, you can't change the sign-on method from SAML to SWA if re-authentication is selected.
+Select Prompt for factor to require users to choose an MFA option, and specify how frequently you want users to be prompted. The Multifactor Settings link takes you to the Multifactor Authentication page, where you can choose your factors.
+Click Save.
+
+"}

okta_dataset_train.jsonl

@@ -0,0 +1,239 @@
+{"text":"### Human: How to create a user in Okta? ### Assistant: In the Admin Console, go to Directory > People.Click Add Person.Select a user type in the User type list.
+Complete these fields:
+First name — Enter the user's first name.
+Last name — Enter the user's last name.
+Username — Enter the user's user name in email format.
+Primary email — Optional. Enter the user's primary email if it's different from their username.
+Secondary email — Optional. Enter a secondary email to allow the user to access information when their primary email is unavailable.
+Groups — Optional. Enter the groups to which the user belongs.
+Password — Select Set by user to allow the user to set their password, or select Set by admin and enter a password.
+Send user activation now — Optional. This check box is available when Set by user is selected as the password option. Select this check box to send a user activation email to the user.
+User must change password on first login — Optional. This check box is selected by default when you select Set by admin as the password option. Clear this check box if you do not want the user to change their password when they first sign in.
+Click Save."},
+{"text":"### Human: How to Install the Okta Active Directory agent? ### Assistant: Download and install the latest version of the Okta Active Directory (AD) agent on your host servers to make sure that you have the most current features and functionality and get optimum performance. If you are running multiple Okta AD agents, make sure they are all the same version. Running different versions within a domain can cause all agents in that domain to function at the level of the oldest agent. This doesn't affect other domains.
+
+To download the agent from another computer, copy the Okta AD agent installer to the host server.
+
+If you're installing the Okta AD agent on a DMZ server, you must open specific ports. See Configure DMZ server ports for Active Directory integrations.
+
+On the host server, open a web browser and sign in to the Okta Admin Console with Super Admin permissions.
+In the Admin Console, go to Directory > Directory Integrations.
+Click Add Directory and then select Add Active Directory.
+Review the installation requirements and click Set Up Active Directory.
+Click Download Agent.
+On the host server, locate and double-click the installer .exe file and complete the installation:
+Click Run when the message Do you want to run this file? appears.
+Click Next.
+Accept the default installation folder, or click Browse and select an alternate location. Click Install.
+Accept the default AD domain you want to manage with this agent, or enter a domain name in the Domain field. Click Next.
+Select a domain user for the Okta AD agent to run as:
+Select Create or use the OktaService account (recommended) and complete the prompt to set a password. Okta recommends using a complex password for security.
+Select Use an alternate account that I specify if you want to assign the Okta AD agent to run as an existing domain user.
+If you're using a group Managed Service Account (gMSA) for the Okta AD agent service account, enter the account name and leave the Password field empty. You must include a dollar sign ($) at the end of the account name. For example, gMSA01$@example.com.
+
+Click Next.
+Optional. Specify a proxy server through which your AD agent will connect.
+If you are installing an AD agent version 3.4.11 or later, in environments where internet traffic is required to go through a proxy, the sign-in flow for the AD agent installer uses the proxy settings specified within the installer. If no proxy settings are specified, the default settings are used.
+Click Next.
+Select a domain to register the Okta AD agent with Okta. To register the Okta AD agent with the Okta service, enter your Okta subdomain name. This is the <mycompany> part of the example: <mycompany>.okta.com.
+Click Next.
+On the Okta Sign In page, enter your admin username and password, and then click Sign in.
+The Okta AD agent requires several permissions. Click Allow Access. The agent installation completes.
+If the error message \"The underlying connection was closed. Could not establish trust relationship for the SSL/TLS service channel\" appears you are likely installing a version of the Okta AD agent with SSL pinning enabled by default and this prevents communication with Okta. This is most likely to occur in environments that rely on SSL proxies. To complete the installation, Okta recommends adding the domain okta.com to an allowlist to bypass SSL proxy processing. You can also disable SSL certificate pinning.
+
+Click Finish.
+When the Okta AD agent starts, return to the browser and click Next.
+Select the configuration options:
+(First time installations for this domain only) On the Connect an Organizational Unit to Okta screen, select the OUs from which you want to import users and groups.
+In the Okta Username format list, select one of these formats that you want AD-imported end users to use when logging in to Okta:
+Email address
+SAM Account Name
+User Principal Name (UPN)
+Custom
+It is critical that the username format selected here be the correct format when you first import users. Changing the value can cause errors for existing users.
+
+Click Next.
+In the Import AD Users and Group dialog, click Next.
+Note: To reconfigure OU and import settings, as well as other settings, return to the Settings tab (Directory > Directory Integrations > Active Directory > Settings). See Configure Active Directory import and account settings.
+
+On the Select the attributes to build your Okta User profile screen, accept the default attributes or select the specific attributes for your Okta user profiles. Attributes can be modified as the needs of your business change.
+
+To learn more about Okta user profiles and attributes, see Work with Active Directory attributes.
+
+Click Next.
+Click Done.
+Define the import, account, and provisioning settings."},
+{"text":"### Human: What is the timezone on Okta access token? Does it follow UTC? ### Assistant : It depends on whether the JWT is verified via the server or the computer. If it is via server, it’s UTC, if it is via computer, you can set it up according to the user’s timezone.
+
+ 
+
+Okta Timezone attribute supports tz timezone database listed here: https://en.wikipedia.org/wiki/List_of_tz_database_time_zones 469. If your HR system has a timezone format different than that of the standard time zone formats, you can create a custom attribute in Okta to map it to the user’s Okta profile. This timezone attribute in Okta can then be mapped and used to sync from Okta to the HR system"},
+{"text":"### Human: How to add an Okta org group? ### Assistant : A group is a logical container for the users associated with an application.
+
+It's a best practice to use groups to organize user access to Access Gateway apps. You can create groups specific to the apps, or reuse existing groups. See Users, groups, and profiles.
+
+To define a group in your Okta org:
+
+In the Admin Console, go to DirectoryGroups.
+Click Add Group.
+Complete the fields in the Add group dialog.
+Click Save.
+Add the people to the group who should have access to the app."},
+{"text":"### Human: How to Manually assign people to a group in Okta? ### Assistant : Assign people to a group to make them members of the group.
+
+In the Admin Console, go to Directory > Groups.
+Select a group in the list, or enter the name of the group in the search field.
+Optional. Perform an advanced group search:
+Click Advanced Search.
+Select a search filter option in the Choose field list. You can filter your search results by created or updated date and time, or you can select base or custom attributes to filter your results.
+Select a filter option:
+Starts with: Select this option to search for group names that start with specific letters.
+Equals: Select this option to search for group names that are equal to the value you enter.
+Greater than: Select this option to search for group names that are greater than the value you enter.
+Less than: Select this option to search for group names that are less than the value you enter.
+Enter a search value in the Value field.
+Optional. Click Add filter to add an additional filter and then repeat steps a to d. Click Clear all filters to clear the ones you have already entered.
+Click Search.
+Optional. Use the Group source type menu to filter results by group source.
+After selecting a group, enter the name of the person in the Search field.
+Optional. Perform an advanced search:
+Click Advanced Search.
+Select a search filter option in the Choose field list. You can filter your search results by created or updated date and time, or you can select base or custom attributes to filter your results.
+Select a filter option:
+Starts with: Select this option to search for names that start with specific letters.
+Equals: Select this option to search for names that are equal to the value you enter.
+Greater than: Select this option to search for names that are greater than the value you enter.
+Less than: Select this option to search for names that are less than the value you enter.
+Enter a search value in the Value field.
+Optional. Click Add filter to add an additional filter and then repeat steps a to d.
+Click Search.
+Click Assign  to assign the person to the group.
+Optional. Select one of these options to assign additional people to the group:
+Repeat steps 4 and 5 to add additional people to the group.
+Click , select Assign all, and select Assign all people in org to assign all people in your org to the group.
+Click More actions, select Assign all people in org, and then select Assign all people to assign all people in your org to the group.
+Click Done.
+Click Back to Groups to return to the Groups page.
+"},
+{"text":"### Human: How to Bulk assign people to a group? ### Assistant : Use a CSV file when you need to quickly assign multiple people to a group. You can bulk assign a maximum of 10000 users to a group at a time.
+
+In the Admin Console, go to Directory > Groups.
+Select a group in the list, or enter the name of the group in the search field.
+Optional. Perform an advanced group search:
+Click Advanced Search.
+Select a search filter option in the Choose field list. You can filter your search results by created or updated date and time, or you can select base or custom attributes to filter your results.
+Select a filter option:
+Starts with: Select this option to search for group names that start with specific letters.
+Equals: Select this option to search for group names that are equal to the value you enter.
+Greater than: Select this option to search for group names that are greater than the value you enter.
+Less than: Select this option to search for group names that are less than the value you enter.
+Enter a search value in the Value field.
+Optional. Click Add filter to add an additional filter and then repeat steps a to d. Click Clear all filters to clear the ones you have already entered.
+Click Search.
+After selecting a group, click Assign people.
+Click More Actions > Assign people via import from CSV.
+Click Browse and then browse to the location of the CSV file.
+Select the CSV file and then click Open.
+Click Upload CSV.
+Click Import and assign.
+A summary of the CSV import listing successful and unsuccessful imports is sent by email to the admin."},
+{"text":"### Human: How to Remove people from a group? ### Assistant : Remove people from a group when they are no longer members of the group.
+
+In the Admin Console, go to Directory > Groups.
+Select a group in the list, or enter the name of the group in the search field.
+Optional. Perform an advanced group search:
+Click Advanced Search.
+Select a search filter option in the Choose field list. You can filter your search results by created or updated date and time, or you can select base or custom attributes to filter your results.
+Select a filter option:
+Starts with: Select this option to search for group names that start with specific letters.
+Equals: Select this option to search for group names that are equal to the value you enter.
+Greater than: Select this option to search for group names that are greater than the value you enter.
+Less than: Select this option to search for group names that are less than the value you enter.
+Enter a search value in the Value field.
+Optional. Click Add filter to add an additional filter and then repeat steps a to d. Click Clear all filters to clear the ones you have already entered.
+Click Search.
+Optional. Use the Group source type menu to filter results by group source.
+Select one of these options:
+Click Remove  to remove a person from the group.
+Click More Options  and click Remove all people in group to remove all people from the group."},
+{"text":"### Human: I have a user setup with multiple required factors to be enrolled (Identity Engine) but when I login in as that user the factors are not being prompted to be enrolled. ### Assistant : For OIE this is different, as long as one of them is meet, then you will not be prompted."},
+{"text":"### Human: What are the different User Statuses in Okta ### Assistant : STAGED - New users created through the API and not activated yet
+PROVISIONED/PENDING USER ACTION - Admin manually activates the user account. The user is in an active state, but has not completed the activation process
+ACTIVE - Active status
+RECOVERY/PASSWORD RESET - Existing user, activated previously, currently in password reset mode. User action required.
+PASSWORD EXPIRED - User password is expired
+LOCKED OUT - User exceeds the number of login attempts defined in the login policy
+SUSPENDED - User cannot access applications, including the dashboard/admin..
+DEPROVISIONED - Deactivated in Okta
+"},
+{"text":"### Human: What is Okta and What Does Okta Do? ### Assistant : Okta connects any person with any application on any device.
+
+It's an enterprise-grade, identity management service, built for the cloud, but compatible with many on-premises applications. With Okta, IT can manage any employee's access to any application or device. Okta runs in the cloud, on a secure, reliable, extensively audited platform, which integrates deeply with on-premises applications, directories, and identity management systems.
+
+The Okta solution was born of the unique challenges of how technology has grown and shifted in the growing diversity of devices, identity issues, security, employee mobility, vender partnership, and the exponential growth of unique application options.
+
+
+
+Okta features include Provisioning, Single Sign-On (SSO), Active Directory (AD) and LDAP integration, the centralized deprovisioning of users, multifactor authentication (MFA), mobile identity management, and flexible policies for organization security and control.
+
+All of these functions are brought together through a network of pre-integrated applications called the Okta Integration Network (OIN). The OIN provides diverse integration options, enabling SSO login for every app your users need to access during their work day.
+
+Active Directory and LDAP Integration
+In the majority of enterprises, Microsoft’s Active Directory (AD) is the authoritative user directory that governs access to key business applications. SaaS applications were developed with their own native user directories, and because they run outside of the firewall, are typically beyond the reach of AD. This limitation requires users to remember multiple usernames and logins, and IT is forced to create, manage, and map user accounts in AD and across their SaaS applications. Okta combats these problems with a complete, robust and easy-to-use AD SSO integration.
+
+Active Directory alternatives include LDAP and other on-premises identity managers. In total, the “Okta solution” overcomes the economic and technological limitations of any legacy identity management scheme you are currently using.
+
+
+
+See a few terms you're not familiar with? See the Okta Terminology page.
+
+Free-Trial Accounts
+It can take less than 30 minutes to get started, but you have 30 days to try using Okta to increase security, improve user productivity, and make your IT team more efficient.
+
+Click Okta free trial to get started.
+
+While using your free-trial account, you can import up to 10,000 users and activate 100 of them. You can also have up to 50 applications on your org. If you need to import and activate additional users or you need more applications, contact Okta support to increase the limitations on your org."},
+{"text":"### Human: What User Statuses Consume an Okta License? ### Assistant : The following Okta user status will count towards an available Okta license:
+
+Active
+Recovery/Password Reset
+Password Expired
+Locked Out
+Suspended
+However, the following Okta user status will NOT count towards an available Okta license:
+
+Staged
+Provisioned/Pending User Action
+​​​​​​​Deprovisioned/Deactivated"},
+{"text":"### Human: What are Okta licenses and what do they contain? ### Assistant : Okta licenses refer to the subscription plans offered by Okta, a popular identity and access management (IAM) platform. These licenses provide access to various features and functionalities within the Okta platform, enabling organizations to manage and secure their users' identities and access to applications and resources.
+
+The Okta licenses are typically divided into different product categories, each tailored to specific identity and access management needs. Here are the main Okta licenses and a brief overview of what they contain:
+
+Workforce Identity Cloud License:
+This license is designed to manage the identities and access of an organization's employees or workforce.
+
+Workforce Identity Products include:
+
+Single Sign-On (SSO): Allows users to access multiple applications with a single set of credentials.
+Adaptive SSO: Provides enhanced security with adaptive authentication measures.
+Multi-factor Authentication (MFA): Adds an extra layer of security by requiring multiple factors for user verification.
+Adaptive MFA: Utilizes contextual information for more intelligent and dynamic multi-factor authentication.
+Universal Directory: Offers a centralized user directory that can integrate with various identity sources.
+Lifecycle Management: Automates user provisioning, deprovisioning, and user lifecycle workflows.
+API Access Management: Manages access to APIs and controls their usage.
+Advanced Server Access: Facilitates secure access to servers and infrastructure.
+Access Gateway: Allows secure access to on-premises and cloud resources.
+Workflows: Enables automation and customization of identity-related processes.
+Customer Identity Cloud License:
+This license is geared towards managing customer identities, providing authentication, and enhancing the user experience for customers accessing an organization's applications and services.
+
+Customer Identity Products may include features like:
+
+Single Sign-On (SSO) and Adaptive SSO.
+Multi-factor Authentication (MFA) and Adaptive MFA.
+Social Identity Integration: Allows customers to log in using their social media accounts.
+Customer Registration and Authentication: Provides registration and login capabilities for customers.
+Customer Consent and Preference Management: Enables customers to manage their consent and preferences regarding data usage.
+Please note that the specific features and functionalities may vary based on the license type and the plan selected by the organization. Okta licenses are typically priced based on a per-user per-month basis, and organizations can choose the license types and features that best suit their identity and access management requirements."},
+
+