Hi Jeff,

I had a quick look at the connector (which looks really cool by the way, kudo's Vasco Santos...see what I did there) and seems like the application is currently setup to work for a single User.

The API used to generate the Token accepts a couple of input parameters. Namely the client Id, client secret, code and grant type. I assume all of these are user specific (excluding the grant type) and are required for the login/authentication process. See http://developers.strava.com/docs/authentication/ for more info on the Strava authentication.

Now, how this is done on the OutSystems side. It looks like the demo is using 2 site properties to store the client id and the client secret. 

Site properties are variables which can be set with a default value at development time, but set to any other value at runtime either programmatically, or by manually changing them in Service Center. The values applied to the site properties will be applied to all users using the application. Think of them as global application 'setting's' of sorts.

There are no default values provided in the Strava example as I am sure Vasco did not want to share this information, however you can set your own details in Service Center. 

Click the gear icon in Service Studio while you have the StravaConnector_CFG module open: 

Login in with your credentials, and then navigate to the Site Properties tab:

Here you will be able to open and set the site properties required for the authentication process. 

I hope this helps.

Thanks,

Nicholas

Hello Jeff.

Usually, that goes into the site properties

Go to Service Center.

In Factory select the Modules and StravaConnector_CFG.

Fill ClientId, ClientSecret.

The token is set on runtime.