SAML #92

Activity

1. zcbenz commented on May 15, 2020

   

   zcbenz

   on May 15, 2020

   Member

   More actions

   Can you do npm i keytar @slack/web-api and then run following code in Node.js:

   require('keytar').getPassword('Slack', 'tokens').then(console.log)

   and do you see a JSON string with token and teamId keys printed?

   (Please do not paste your token here.)

   And if tokens are printed, can you try running following code to see if the token can be used?

   (new (require('@slack/web-api').WebClient)('xoxs-your-token')).auth.test().then(console.log)
2. Poil commented on May 15, 2020

   

   Poil

   on May 15, 2020

   Author

   More actions

   Hi,

   No token/teamId found

   require('keytar').getPassword('Slack', 'tokens').then(console.log)
   Promise {
     <pending>,
     domain:
      Domain {
        domain: null,
        _events:
         [Object: null prototype] {
           removeListener: [Function: updateExceptionCapture],
           newListener: [Function: updateExceptionCapture],
           error: [Function: debugDomainError] },
        _eventsCount: 3,
        _maxListeners: undefined,
        members: [] } }
   > null
   
3. zcbenz commented on May 15, 2020

   

   zcbenz

   on May 15, 2020

   Member

   More actions

   It seems that slack handles SAML login differently than normal login.
4. Poil commented on May 15, 2020

   

   Poil

   on May 15, 2020

   Author

   More actions

   Via a webbrowser, I'm able to get the xoxc-********** header and the cookie that contains d=
   How keytar works ?
5. zcbenz commented on May 15, 2020

   

   zcbenz

   on May 15, 2020

   Member

   More actions

   keytar reads from system keychain, it is possible that Slack generates a new token for SAML every time and does not store the token in system keychain.