How do you handle SEN / license validation in JSM today?

[#1]

If you're an Atlassian Marketplace vendor running customer support through JSM, you've probably felt this pain: a customer opens a ticket and you have no idea upfront whether they're actually a licensed user or which entitlements they have.

The only app I know of that solves this is Connect-based – which means it's on borrowed time and also requires a bunch of customfields to be created.

I just finished building a little Forge-native solution for exactly this use case. Setup is just your Vendor API token and Vendor ID – no custom fields, no manual mapping. The app pulls license and entitlement data directly into the JSM portal view when a request comes in.

Submitting to the Marketplace today as a Free App. 

when the connection has been established:

What a customer will see when filing a request via your JSM Portal.

Background calls against customer atlassianID (respecting technical contacts as well)

Work Item View (Agent side)

Curious how others are handling this right now – manual lookup in MPAC?

A custom workaround? Or just living with the friction?

Have a nice rest of the Weekend

cheers

cF

[C_ Faysal_CFcon_]

i figured this is not possible to share due to "security" complains when attempting to store your own MPAC API token in a forge app. this must be the reason this was solved by switching to a Connect solution

any idea if Atlassian plans to update the OAuth strategie on marketplace API?

regards