Skip to content

Conversation

lcwiklinski-r7
Copy link
Collaborator

@lcwiklinski-r7 lcwiklinski-r7 commented Oct 16, 2025

https://rapid7.atlassian.net/browse/SOAR-20191

  • Replaced the existing Reset Password action with Expire Password
  • Added a new Reset Password action
  • Adjusted and added unit tests accordingly

I was able to run both manual tests and tests in InsightConnect successfully.

  • First, I tested the modified action from reset password (old) to expire password. It behaves the same as before - for example, it generates a temporary password. The existing unit tests also pass successfully. However, since the responses are mocked, I had to verify this manually as well.
  • For the newly added reset password action, I tested two scenarios: one where Okta sends a reset password email to the user, and another where no email is sent - in that case, the response includes a password reset link. The link works correctly and behaves the same as the one sent via email. Unfortunately, I wasn't able to test the revoke sessions functionality. It seems that our Okta instance has expired, so I can't log in to the dashboard; however, the API communication still works.

@lcwiklinski-r7 lcwiklinski-r7 requested a review from a team as a code owner October 16, 2025 07:50
@simonirwin-r7
Copy link
Contributor

simonirwin-r7 commented Oct 16, 2025

Snyk checks have passed. No issues have been found so far.

Status Scanner Critical High Medium Low Total (0)
Licenses 0 0 0 0 0 issues
Open Source Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@lcwiklinski-r7 lcwiklinski-r7 force-pushed the SOAR-20191-Okta-plugin-improvement branch from e94025c to ec7c95f Compare October 16, 2025 08:58
provider that allows companies to integrate their central user account system with
a wide variety of other applications and services'
version: 4.2.16
version: 5.0.0
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wonder if this should be 5.0.0 or 4.3.0 😃

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the validator forced me to push it to 5.0.0

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah I think because the action schema has changed it's treated as a breaking change


#### Expire Password

This action is used to this action expires the password for Okta user and transitions user status to PASSWORD_EXPIRED,
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this wording needs updated

Suggested change
This action is used to this action expires the password for Okta user and transitions user status to PASSWORD_EXPIRED,
This action is used to expire the password for Okta user and transitions user status to PASSWORD_EXPIRED,


This action is used to this action resets password for Okta user and transitions user status to PASSWORD_EXPIRED, so
that the user is required to change their password at their next login
This action is used to this action resets the password for an Okta user using a one-time token (OTT), transitions the
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same here, I think the first portion gets generated so it's just doubled here.

provider that allows companies to integrate their central user account system with
a wide variety of other applications and services'
version: 4.2.16
version: 5.0.0
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah I think because the action schema has changed it's treated as a breaking change

validate(actual, self.action.output.schema)
self.assertEqual(actual, expected)

@parameterized.expand(
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

minor but could just set these without parameterized?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants