Refresh token during Spring Boot and OAUTH2 SalesForce session

Question

I am connecting to SalesForce rest API and with Spring's oauth2template it works really well. I am using Spring Boot, so it is basically just autowiring the Oauth2RestTemplate and configuring the oauth2 properties, but there is a challenge and I am not sure if it is a bug or something I haven't configured properly. The case is when the token expires on the SalesForce side. I still have the old token in the oauth2 context, so if I want the framework to acquire a new token, I manually have to nullify the accesstoken and set it as null in the context in order for getAccesstoken to call acquireAccessToken in the OAuth2RestTemplate class. I know this is wrong, but I suspect it is because I receive missing token information when I first acquire the token from SalesForce. This is the response when I acquire the token the first time

{
    "access_token": "<LONG_VALUE>",
    "instance_url": "<SALESFORCE_SERVER>",
    "id": "<ID_URL>",
    "token_type": "Bearer",
    "issued_at": "1538640612182",
    "signature": "<SIGNATURE_ID>"
}

I cannot get the refresh_token value from SalesForce. I think this is why my OAuth2AccessToken does not have an expiration Date. When I call getExpiration to see the Date, it is null.

So what could I do here? Is there any other configuration I am missing here? I don't like to continue with hacking the framework when it is supposed to handle everything for me, especially acquiring a new token when it expires.

Answer 1

My first question was deleted since no one were able to answer the question, however I would like to propose a solution myself. I think the world needs to know, but I would also love to get some feedback to the solution.

Apparently SalesForce can be set up with a refreshtoken response when you retrieve the token, but in my case I didn't get the refreshtoken. So anyway. In order to work with something that kind of resembles a refreshtoken strategy I created a Date as a bean in my Spring app:

@Bean
    public Date expiryDate() {
    ... Date configuration here ....

The date would be sometime in the future

And then whenever you have to check for expiry, you just check whether today's date exceeds the date from the expiryDate bean. That's how you could avoid Spring's OAUTH2 framework to acquire a new accesstoken from the server everytime. It is a kind of a hacked solution (I know), but it is a way of saving too many calls.