Auto Authentication: Redirect URLs and Persistent Client IDs
8 years, 8 months agoJustin P
Guest
I’m trying to connect the web app I’m working on to Smart Vault, but I’m running into a few stumbling blocks.
Firstly, is it possible to specify a redirect URL for Smart Vault to send a user back to my application? Using the /auto/usr/<email> I’m able to get a URL where a user can authorize the app to connect to Smart Vault. Can Smart Vault post back or redirect back after the user has granted permissions?
Secondly, is it possible to have persistent client IDs? The documentation I’ve read suggests that the client ID needs to be requested periodically (~every day). Other APIs such as Box, and ShareFile use a system where the client ID is static and only the access token changes (this is along the lines of the “Oauth I’m used to”.
