Make "expiration time" to be configurable in BoxDeveloperEditionAPIConnection #1114

Activity

1. ozhelezniak-talend

   added

   enhancementAdded to issues that describes enhancementsAdded to issues that describes enhancements

   on Oct 14, 2022
2. ozhelezniak-talend

   assigned

   antusus

   ,

   arjankowski

   ,

   bartlomiejleszczynski

   ,

   lukaszsocha2

   ,

   mhagmajer

   and

   mwwoda

   on Oct 14, 2022
3. lukaszsocha2 commented on Oct 14, 2022

   

   lukaszsocha2

   on Oct 14, 2022

   Contributor

   More actions

   Hi @ozhelezniak-talend,
   I assume you using OAuth2 authentication type and you are referring to the expiration time of "short-lived authorization code" described here. If not please describe your issue with more details.
   The expiration time of "short-lived authorization code" is defined in authentication server and it is not possible to change this setting by client (SDK). If this is a problem you can also try another authentication methods: JWT or Client Credentials Grant.
   @lukaszsocha2
4. ozhelezniak-talend commented on Oct 14, 2022

   

   ozhelezniak-talend

   on Oct 14, 2022

   Last edited by ozhelezniak-talend

   Author

   More actions

   Hello @lukaszsocha2
   Sorry for the lack of details.
   I'm using JWT authentication method.

   BoxDeveloperEditionAPIConnection.getUserConnection(userId, boxConfig, null)
   

   And when it tries to establish connection a bit deeper into stacktrace

   connection.tryRestoreUsingAccessTokenCache();
   

   it calls method

   this.authenticate();
   

   inside it contains those lines

               // Reconstruct the JWT assertion, which regenerates the jti claim, with the new "current" time
               jwtAssertion = this.constructJWTAssertion(jwtTime);
   

   where inside constructJWTAssertion you can find this hardcoded 30 seconds period

           if (now == null) {
               claims.setExpirationTimeMinutesInTheFuture(0.5f);
           } else {
               now.addSeconds(30L);
               claims.setExpirationTime(now);
           }
   
5. lukaszsocha2 commented on Oct 14, 2022

   

   lukaszsocha2

   on Oct 14, 2022

   Contributor

   More actions

   Hi @ozhelezniak-talend,
   now it is much more clear what you mean :). I will discuss the change with the team, but I believe we can make that configurable with the next release. I'll let you know what we decided.
   @lukaszsocha2
6. lukaszsocha2 commented on Oct 17, 2022

   

   lukaszsocha2

   on Oct 17, 2022

   Contributor

   More actions

   Hi,
   we created internal ticket to address your request (SDK-2704). We will plan it and resolve as soon as our schedule will allow for it.
   Best

   👍React with 👍1Reacted by Oleksandr Zhelezniak