Okta Adaptive MFA gives companies flexible authentication

How is Okta Adaptive MFA adaptive?

Okta Adaptive MFA features risk-based authentication that uses contextual access policies. Based on a user’s location, IP address or device, Okta Adaptive MFA is able to provide the right step-up authentication factor to provide the user with secure access. Admins can define the types of factors users need for access based on their role in the company.
Among other authentication methods, Okta’s MFA product supports push-based and soft token authentication. Through a partnership with Yubico, users also have the option of hard token authentication with YubiKeys.

Learn more at: http://searchsecurity.techtarget.com/feature/Multifactor-authentication-products-Okta-Verify

3 Ways to Use Okta and Workato for Amazing Integrated Identity and Access Management

The Okta connector enables a range of innovative business processes that you can automate from Workato, including Okta acting as a trigger for downstream actions, like multi-channel notifications, sophisticated integrations such as provisioning, or polling Okta for identity information to enable secure workflows. The connector also enables Okta to act as a consumer of events and data from other apps, like HR, Service Management, SIEM, and more.

1) Take action based on events in Okta.

2) Automate employee and partner lifecycle workflows from end-to-end.

3) Do everything from Slack using Workbot.

Learn more at: https://www.workato.com/blog/2017/08/okta-workato-identity-and-access-management

 

One Cloud Access Manager Integration with password management applications

One Cloud Access Manager allows you to integrate with password management solutions adding a forgot password link. Below screenshot that shows you how to configure.

1. By Default the One Cloud Access Manager doesn’t provide a link for the password management solution. You can see screen below.

2. Go to the Admin Interface for  the tool and select Settings | Turn Features On/Off

3.Now you will see the Password Management Options available. For this example, introduce the default password manager link for Quest.

4. Now go to the End User Portal, at this point you will see  a new link called Forgot Password that will redirect you to the Password Management Solution.

5. After you clicked the Forgot Password link on the One Cloud Access Manager, you will be redirected to the Password Management tool.

Keep visiting our Cloud Identity and Access Management blog, we are posting new material every week.

Okta – Installing the Okta LDAP Agent

Okta allows companies to connect to their LDAP directory in order to provide users for Cloud SSO operations. The first step to configure is to install the LDAP Agent, following the steps required to complete the installation.

 

  1. Download the Okta LDAP Agent in the server that will function as LDAP Agent Proxy.

 

2. Once Okta LDAP agent downloaded, start the installation. Click next in the initial page.

3. Review the Okta LDAP Agent agreement and click next.

4. Specify the folder location  where the Okta LDAP Agent will be installed and click Next.

5. Okta LDAP Agent will start the installation files. Wait until is completed.

6. Once completed, you need to configure your LDAP parameters. For this steps we will connect Okta with JumpCloud which is an DaaS ( Directory as a Service )

7. Complete the parameters and click Next. The Okta LDAP Agent will continuing the setup.

8. Now you can configure the Okta LDAP Agent proxy server. You can skip this step if you are planning to use direct connection.

9. Now introduce the values corresponding to your company Okta  URL organization and click Next.

 

10. The Okta LDAP Agent will redirect you to authenticate to your Okta organization. Introduce admin credentials and click Sign In.

11. Okta LDAP Agent will ask permission for the agent. Click Allow Access.

12. Now Okta LDAP Agent will register the agent in your Okta organization.

13. Once the Okta LDAP Agent registration is completed. Now the agent installation is completed. Click finish.

14. Okta LDAP Agent will display a form with the LDAP agent started.

15. At this point Okta LDAP Agent is already installed and registered in your Okta organization. Now you can proceed with the configuration steps. Below a screen within your Okta organization that confirm the Okta LDAP Agent was installed.

 

We will continue this post later with the configuration steps, we will use JumpCloud LDAP capabilities.

 

Disable Okta Home footer

Disable Okta Home footer

By default Okta enable the home footer. This footer can be disabled  if is required by the business.

 

To disable the Okta footer, login the Okta instance as a admin and to to the Settings | Appearance Menu

In the Display option select the drop down component and select disable.

 

Now login or refresh the Okta page for a logged user and you will see the changes.

 

How to delete a user within okta?

Okta recently released a new feature that allow delete the user from their cloud tenant. Below screenshot showing the okta delete button.

1. Login to the okta admin console and under the Directory Menu select People. From there select the user link to edit. Now you will see the Delete button.

cloud_identity_okta_4_1

2. Once you click the okta Delete button, a confirmation windows will be displayed Click Delete and now your user will be deleted.

cloud_identity_okta_4_2

 

The delete button will only appears if the user was previously deactivated.

JumpCloud System – User bindings for windows systems

JumpCloud System – User bindings for windows systems

1. JumpCloud cloud solution for IDaaS allows you to add windows systems using an agent installed on them. Once the system exist within jumpcloud, now you have to configure the user. You go to the System option and select the system, from here you select the user you want to allow access the windows system and choose if you want to allow access as a Standard User or Administrator.

cloud_identity_jumpcloud_2_1

2.Once JumpCloud save the changes. Now you can remote access the server with the user.
cloud_identity_jumpcloud_2_2

3. Now you should have been logged within the windows systems. If you go to the Control Panel and verify the user account now exist.

cloud_identity_jumpcloud_2_3