Is it possible to force users to be logged out to help with a caching issue?

[mshannon93]

Hi

We recently separated our API keys within a parent site so that our mobile apps and website were all on separate keys (as children within the parent). Previous to that our mobile apps (iOS and Android) shared the same key as our website. We wanted to make certain account schema fields have different rules on website v mobile so we separated the keys.

Our mobile app code does not force our fans to be logged out after a period of time and therefore even after our fans updated to the latest app version (with the new API key) they're having some account issues. This can be resolved by logging out and logging back in.

However, we have close to 500,000 users and to ensure a smooth transition I would like to force log out our users so that it reduces any potential issue with the switching of the keys. I know this is possible via our app configs but I was curious if there might be a quicker way via Gigya.

Thanks

[SebastianSchuck19]

Hey mshannon93,

alternatively you could ultilize the accounts.logout method. However you'll need to figure out a way to only select the active app users when using something like a Dataflow (ETL). At which point I guess relying on the app configs might be the easier option.

Best,
Sebastian Schuck

[mshannon93]

Hey Sebastian,

Thanks for the advice with this one - are you suggesting that we could setup a dataflow that selects accounts (active) and then the action would be to trigger the accounts.logout method? Would this then log them out across digital products that we use the Gigya login API?

Thanks!