SCIM provisioning: Blameless-Okta integration

Feature Releases

Identity management

SCIM provisioning: Blameless-Okta integration

Does your organization manage user access across multiple SaaS services? If so, then more than likely you're using a third-party authorization provider like Okta to centrally manage your users. Good news! We are happy to announce that you can now manage Blameless user groups directly from Okta via our new SCIM integration capabilities.

Key features include:

• User activation
• User deactivation
• Group pushing
• Group linking
• User to group bi-directional updating (when groups are linked)

At a high level, the process works as follows:

1. Create your groups in Okta.
2. Assign your application for authorization to Blameless for each group.
3. Assign multiple users to a group within the groups tab in directory.
4. Select and push these groups to Blameless.
5. Visit your Blameless instance to see your groups and the users you selected.
6. Apply permissions to the group within Blameless that reflects the needs of your group.

Please see Okta to learn how to integrate Okta and Blameless. Additionally, to get up-to-speed on creating groups and adding users in Okta, please see User Management with Okta.

‍

Bug Fixes

Slack

Starting an incident fails from a private channel without the Blameless app

Issue:

When attempting to start a Blameless incident from a private channel without the Blameless app added to it, the /blameless start incident command allowed users to open and complete the Start incident modal, but the creation of the incident would fail after submitting the request.

Fix:

Now, the following warning message is displayed in the private channel when users attempt to run any /blameless command when the Blameless app has not been added to it:

Additionally, the following warning message is displayed in direct messages when users attempt to run any /blameless command when the Blameless bot user had not been invited to that direct message channel:

Incident types

Once the auto assigned role to a creator is set to a role, it can no longer be reset to none

Issue:

In Settings → Incident Types, after selecting a new default incident role for an incident creator, users were no longer able to change it back to None.

Fix:

Users can now reset the default incident role for the creator of an incident to None from any previously-saved value.

Jira

The links to the Blameless incident and the incident channel in Slack no longer appear in the Jira ticket Description field

Issue:

When the integration with Jira was enabled in your Blameless account, the Description field in auto-created Jira tickets (per Blameless incident) stopped including both a link to the Blameless incident and the incident channel in Slack.

Fix:

If the integration with Jira is enabled in your Blameless account, both links to the Blameless incident and the incident channel in Slack now appear in the Description field for each auto-created Jira ticket (when a Blameless incident is created).

‍