/

Atlassian Jira Service Management (JSM)

Atlassian Jira Service Management (JSM)

Integration type

Helpdesk

What we solve

Jira Service Management teams need a secure, auditable way to verify a requester’s identity before granting high-risk access (account recovery, privileged production access) because tickets alone don’t prove the requester is the right person. This integration uses Jira Automation + HTTP actions to trigger 1Kosmos BlockID Verify and LiveID from specific request types, posts the verification link into the ticket, consumes webhook results, and automatically approves/denies or routes issues based on verified status—reducing social engineering risk and speeding up secure access escalation.

Platform identity landscape

Jira Service Management is the ITSM extension of Atlassian's platform, with deep adoption among software-led organizations and DevOps teams. JSM's primary strength is its integration with Jira Software — incidents, requests, and changes can be linked directly to engineering tickets. JSM uses Jira Automation for no-code workflow rules and supports Atlassian Connect apps for marketplace integration.

The IDV use case in JSM is concentrated in two areas: developer account recovery (engineers locked out of GitHub, AWS, or internal systems) and access escalation for production environment deployments.

JSM Service Request: "Request elevated access to production Kubernetes cluster"
    -> Jira Automation rule: Issue Created, Request Type = "Prod Access"
    -> Automation HTTP POST: /v2/verify/sessions
    <- { session_id, verification_url }
    -> Automation: Add comment to JSM ticket: "Please verify your identity: [verification_url]

JSM Service Request: "Request elevated access to production Kubernetes cluster"
    -> Jira Automation rule: Issue Created, Request Type = "Prod Access"
    -> Automation HTTP POST: /v2/verify/sessions
    <- { session_id, verification_url }
    -> Automation: Add comment to JSM ticket: "Please verify your identity: [verification_url]

JSM Service Request: "Request elevated access to production Kubernetes cluster"
    -> Jira Automation rule: Issue Created, Request Type = "Prod Access"
    -> Automation HTTP POST: /v2/verify/sessions
    <- { session_id, verification_url }
    -> Automation: Add comment to JSM ticket: "Please verify your identity: [verification_url]


Transform how you verify and authenticate

Secure onboarding, eliminate passwords, and stop fraud on one platform. Schedule a demo and see it in action.

Transform how you verify and authenticate

Secure onboarding, eliminate passwords, and stop fraud on one platform. Schedule a demo and see it in action.

Transform how you verify and authenticate

Secure onboarding, eliminate passwords, and stop fraud on one platform. Schedule a demo and see it in action.