Skip to main content

OpenAM Shell REST Client

Last week I updated my OpenAM Shell REST client to not only use the newer REST endpoints of v11, but also added an interactive menu, similar to what I had added to the OpenIDM client and OpenDJ one too.

The client was to really test the new API and see what endpoints had been added.  The biggest difference in v11 is the ability to use callbacks within the authentication module response, allowing other attribute values to be passed back to OpenAM, instead of the traditional username and password values.

The client is just a collection of individual shell scripts that call curl and jq for additional JSON parsing.

JQ isn't really needed as OpenAM now offers a
_prettyPrint=true parameter that can do some basic JSON parsing before the response is delivered.  JQ is just useful if you want to iterate over object that comes back and pull out specific attributes.

I then added a simple menu system, just using case, with each menu having it's own file, just to keep the management easy.  A bit of OO in bash :)

To use, simply either download via Github as a zip or clone the repo.  Run ./interactive.sh to get started (albeit you can still run each script individually).  Add in your OpenAM server settings via option 'C'.  Away you go.  You need to authenticate to do anything.  Authenticating via any method, will create a .token file in the shell client directory which is then reused during subsequent calls to OpenAM as a header value.

You can authenticate to any realm, module or service and then check that your current token is valid.

You then retrieve the attributes associated with that token, before going onto managing objects within then OpenAM repo such as realms, agents, users and so policies.

There are basic create-read-update-delete menus for users, realms and agents, that are simply based on the HTTP verbs GET and PUT.  Creating objects I've simplified by allowing the new object to be added to a JSON file and simply pulled up via a PUT using the _action=create parameter.

For further details on the OpenAM REST client endpoints, take a look at chapter 3 of the Developers guide available at ForgeRock documentation site.

Comments

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

Set Session Limits Using Context

Session limits typically cover 4 main items: total number of sessions a user can have at any one time, the max length of each session, the max idle time and max caching time. In an out of the box deployment in ForgeRock AM, these settings are configured via the session service.  However there are few tweaks than can be made to allow these settings to be run via a per user or per tree flow.  For example. think of the following scenario - user is logging via a device, location or network that has a higher risk rating.   Perhaps you would like to reduce session length on a BYOD device running an out of support version of Android to have a length of only 15 minutes.  If they switched back to their main trusted device, we can spin that back to 1hr. Another example, could be the spotting of a higher suspicion of bot activity for a particular user.  Maybe we need to set the entire quota limit to 1, to stop a bot spawning multiple sessions with the same credentials. This is all pretty trivial