You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am working on a version 3 of summit that will use vue components that will work natively with Terrain's router and state. I thought that would be a good time to try to setup a way to automatically login to Topo from Summit/Terrian. Here is a sample vue component I wrote that should be able to encrypt the auth token with a public key and send it to topo in a new tab: https://github.com/pete-mc/Summit/blob/3.0.0-react/summit-app/src/components/topo.vue
Here is a gist on how you could implement it on your side: https://gist.github.com/pete-mc/6616dfb7f71b62f3e0c86f1acd2fe917
On your side it verifies terrain as the caller and has a CORS policy as an extra layer, then it decrypts it with a private key that should be secure on your server and then you can do whatever you need to from there.
Happy to consider other security options too. I am looking to have v3 ready for testing in a 4 to 8 weeks. I could add this to a dv branch of v2 in the meantime if you want to get stuck into it sooner.
The text was updated successfully, but these errors were encountered:
Hey @NomisNostab,
I am working on a version 3 of summit that will use vue components that will work natively with Terrain's router and state. I thought that would be a good time to try to setup a way to automatically login to Topo from Summit/Terrian. Here is a sample vue component I wrote that should be able to encrypt the auth token with a public key and send it to topo in a new tab: https://github.com/pete-mc/Summit/blob/3.0.0-react/summit-app/src/components/topo.vue
Here is a gist on how you could implement it on your side: https://gist.github.com/pete-mc/6616dfb7f71b62f3e0c86f1acd2fe917
On your side it verifies terrain as the caller and has a CORS policy as an extra layer, then it decrypts it with a private key that should be secure on your server and then you can do whatever you need to from there.
Happy to consider other security options too. I am looking to have v3 ready for testing in a 4 to 8 weeks. I could add this to a dv branch of v2 in the meantime if you want to get stuck into it sooner.
The text was updated successfully, but these errors were encountered: