Creating Aria Operations for Logs Users without SMTP

Part of the Aria Operations for Logs deployment is configuring an SMTP server, which is used to notify new users of their account creations. When a new user is created they receive an email similar to this.

They will then click the link and reset their password.

They will set their password and be sent into Operations for Logs.

But what if there is no SMTP server? No problem, the local admin can set the user password and assign Roles once the userid has been created via API, let's try it. The Aria Operations for Logs API surface can be found at https://your_logs_name/rest-api/supported and will look like this.

Scrolling down, you'll see all of the API endpoints along with a button called Authorize, which is what you'll use to authenticate.

We covered this in a previous blog, but the Authorize button will ask for a Session ID or Bearer Token.

As indicated in the Authorization stanza up above, the Session ID is an opaque bearer token valid for a limited period of time, obtained via POST /sessions, mine looks like this.

Now that we have our Session ID, we will use that to authenticate.

Once authenticated, we can list all users with GET /users.

Which you can see is still in PENDING_PASSWORD_CHANGE status as we can't send out email notifications to the new user to reset their password without an SMTP server. So, let's just reset that users password via the users endpoint, specifically PATCH /users/{userid}/password, which requires the {userId} paramter from the previous call. Mine looks like this.

Now let's go login.

And we're in!

All sorts of other things you can do via the Operations for Logs API surface, this is just one of them, enjoy!