Skip to main content

Building a Password Checkout Service in OpenIDM

A common use case within the identity life cycle management world, is what to do with shared and privileged accounts.  Common accounts such as administrator, root, backup operator accounts and other delegated administration accounts, lead to a significant anti-pattern approach when it comes to password management.  For example, many shared service or administration accounts....are just that: shared.  Sharing a password is a very insecure method of account administration.

This generally brings out several security issues:

  • The password is generally none-complex in order for many users to remember it
  • The sharing of the password is not tracked - people who shouldn't know the password generally do
  • It's difficult to track who is actually using an account at any moment in time
Whilst these issues are well known...they are still prevalent, and hence an entire sub industry focused on privileged account management (PAM).

Whilst OpenIDM isn't a PAM product, some basic password checkout service use cases can easily be coded out using the custom endpoint component, in a few lines (say 150!) of JavaScript.

The above flow was implemented via a single custom endpoint - the Password Checkout Service. This service basically leverages some of the core functionality of OpenIDM, such as the scheduler, OpenICF connectors, policy engine and role based access control model.

The PCS is a few JavaScript files that basically does a few things.  Firstly it applies an RBAC constraint on who can use the service - simply driven by a role called passwordCheckoutService. 

Only members of the role can use the service.  The PCS then checks a white list for accounts the PCS can work against - we don't want to be resetting the password of a normal user! This white list exists in a a CSV called pcsValidAccounts. The PCS then checks it's request store - pcsRequests.  This store contains records of the following format: 

  • requestId - unique reference for that particular request
  • requestTime - time stamp 
  • account - userid of the account being checked out
  • accountPath - the OpenIDM reference to where the account sits
  • checkoutActive - is the current checkout still alive (boolean)
  • checkedOutBy - userid of the user performing the check out
  • resetTime - time in the future then the account will be reset

This demo stores the above in a CSV file using the out of the box connector, but a SQL connector could equally be used in production pretty easily.

Configuration is available for the following items:
  • duration an account can be checked out for (minutes and hours)
  • the length of the password to be issued
  • number of upper case chars in the issued password
  • number of numbers in the issued password
  • number of special chars in the issued password
The checked out passwords are notified to the calling user in the JSON payload, but could easily be sent via the OpenIDM email service, to a pre-registered email address to add a little more security.

The PoC-level source code is available here.


Popular posts from this blog

WebAuthn Authentication in AM 6.5

ForgeRock AccessManagement 6.5 , will have out of the box integration for the W3C WebAuthn . This modern “FIDO2” standard allows cryptographic passwordless authentication – integrating with a range of native authenticators, from USB keys to fingerprint and facial recognition systems found natively in many mobile and desktop operating systems. Why is this so cool? Well firstly we know passwords are insecure and deliver a poor user experience. But aren’t there loads of strong MFA solutions out there already? Well, there are, but many are proprietary, require complex integrations and SDK’s and ultimately, don’t provide the level of agility that many CISO’s and application designers now require.  Rolling out a secure authentication system today, will probably only result in further integration costs and headaches tomorrow, when the next “cool” login method emerges. Having a standards based approach, allows for easier inter-operability and a more agile platform for chan

Implementing Zero Trust & CARTA within AM 6.x

There is an increasing focus on perimeterless approaches to security design and the buzzy "defensive security architectures".  This blog will take a brief look at implementing a contextual and continuous approach to access management, that can help to fulfil those design aspirations. The main concept, is to basically collect some sort of contextual data at login time, and again at resource access time - and basically look for differences between the two.  But why is this remotely interesting?  Firstly, big walls, don't necessarily mean safer houses.  The classic firewall approach to security.  Keeping the bad out and the good in.  That concept no longer works for the large modern enterprise.  The good and bad are everywhere and access control decisions should really be based on data above and beyond that directly related to the user identity, with enforcement as close as possible to the protected resource as possible. With Intelligent AuthX, we can start to collect an

Forget Passwordless, What About Usernameless?

A year or so ago, I blogged about the wonderful world of passwordless and how WebAuthn  was going to save the world!  Gone will be insecure passwords, with their terrible user experience, and contributions to data breaches and in with a standards driven, crypto based, technology agnostic way of authenticating a user. The panacea!  Well, the panacea might just be getting be getting a little better. Take a look at the above blog for a quick "reccy" on how WebAuthn works and the main flows.  TLDR; we're using public/private key pairs for each website or service we want to authenticate against.  The private key gets stored somewhere safe - namely within the dedicated USB authenticator fob, or within the secure element on an operating system. In ForgeRock Access Management 7.0 EA, the WebAuthn registration authentication node has been modified to now include a "Username to device" switch.  This essentially allows a user handle to be sent back down to the authenti