Without the ability to specify the organizationId in the session token request if the user has accounts in multiple orgs then you cannot control the oragnization id that the token is issued for
Note that the organizationId is also missing from the API spec:
https://dev.splunk.com/observability/reference/api/sessiontokens/latest#endpoint-create-session-token
but definitely exists as we use it in other repos that use curl rather than the go client
Without the ability to specify the organizationId in the session token request if the user has accounts in multiple orgs then you cannot control the oragnization id that the token is issued for Note that the organizationId is also missing from the API spec: https://dev.splunk.com/observability/reference/api/sessiontokens/latest#endpoint-create-session-token but definitely exists as we use it in other repos that use curl rather than the go client