You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a user which is logged in through a (server-to-server) connected app with setting "Issue JSON Web Token (JWT)-based access tokens for named users" true tries to use a Logger.xxx method, a Salesforce System Error is thrown.
Debugging learns that these actions fail on calling System.UserInfo.getSessionId() (used in Logger.setTransactionQuiddity).
Current bypass is to set "Issue JSON Web Token (JWT)-based access tokens for named users" false, or to add try/catch arround System.UserInfo.getSessionId().
The text was updated successfully, but these errors were encountered:
@dvanlooy thanks for reporting this! @jamessimone and I have made several attempts at trying to work around some of the issues related to sessions, it seems like the fun never ends! 😅
It looks like you're on an older version of Nebula Logger, but even in the newer versions, it's still relying on System.UserInfo.getSessionId() - I like your idea of adding a try/catch around it, that should be fairly simple to implement. I'll work on getting this changed ASAP.
…WT enabled (#604)
* Fixed#598 by adding a try-catch block around the call to System.UserInfo.getSessionId()
* Optimized how Logger.TRANSACTION_QUIDDITY is loaded so it doesn't repeatedly try to load in transactions where there isn't an active quiddity
* Removed some extra copy-pasta in the new LoggerParameter__mdt record DefaultLogEntryRelatedListFieldSet
@dvanlooy I've just released changes for this in release v4.12.3. Once you're able to upgrade & test it out, please let me know if you run into any more issues!
Package Edition of Nebula Logger
Unlocked Package
Package Version of Nebula Logger
4.8.2
New Bug Summary
When a user which is logged in through a (server-to-server) connected app with setting "Issue JSON Web Token (JWT)-based access tokens for named users" true tries to use a Logger.xxx method, a Salesforce System Error is thrown.
![Screenshot 2024-01-18 at 11 16 37](https://private-user-images.githubusercontent.com/17290962/297704799-a134d4dd-4b9f-4265-9d2c-40fb31780cbb.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjQxMjUxOTQsIm5iZiI6MTcyNDEyNDg5NCwicGF0aCI6Ii8xNzI5MDk2Mi8yOTc3MDQ3OTktYTEzNGQ0ZGQtNGI5Zi00MjY1LTlkMmMtNDBmYjMxNzgwY2JiLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA4MjAlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwODIwVDAzMzQ1NFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTNiN2M3MzBkNTA1ZTU4MjRiODM5NjQxNzljMGJlZDViM2MyMDg0NzkxN2RlOWIyYzMxMWI3NGUxMGJiMjA3YmYmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.uaw_3GfgYiGQ4Ikf_7dyIZcaZJKbYKPPysadc0qYXo8)
![Screenshot 2024-01-18 at 10 48 20](https://private-user-images.githubusercontent.com/17290962/297704150-4f3a1094-5e48-4815-9ac7-13f7ab7f49ca.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjQxMjUxOTQsIm5iZiI6MTcyNDEyNDg5NCwicGF0aCI6Ii8xNzI5MDk2Mi8yOTc3MDQxNTAtNGYzYTEwOTQtNWU0OC00ODE1LTlhYzctMTNmN2FiN2Y0OWNhLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA4MjAlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwODIwVDAzMzQ1NFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTYxZmNhZDViMWY0MGNmOTkwYjUyODZiODE0ZmQxODk0OGM5NWE1MzNkODg3NTVhMGJmNThlMDdlZjRiMTRjNzYmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.-c8kJni5seDPApqVgseogZfPF9L5ffGOYpYMBOuI5Vc)
Debugging learns that these actions fail on calling System.UserInfo.getSessionId() (used in Logger.setTransactionQuiddity).
Current bypass is to set "Issue JSON Web Token (JWT)-based access tokens for named users" false, or to add try/catch arround System.UserInfo.getSessionId().
The text was updated successfully, but these errors were encountered: