- Mais recentes
- Mais votos
- Mais comentários
Hi,
maybe another option for you: use AWS Identity Center (via SageMaker) - formerly known as AWS SSO - as identity provider to Snowflake:
lots of applications already integrated https://docs.aws.amazon.com/singlesignon/latest/userguide/saasapps.html
Snowflake itself has an article to describe how to do it: https://community.snowflake.com/s/article/How-To-Configure-AWS-Single-Sign-On-as-an-Identity-provider-for-SSO-with-Snowflake
Currently facing the same issue. Or actually worse, since the "externalbrowser" authenticator does not work in my local browser, as it redirects me to snowflake which is not reachable over public internet in our setup. Didier_Durand's answer would by the way not work, as the cell is in a pending status until the response URL is returned, making it impossible to do custom parsing/handling here.
Conteúdo relevante
- AWS OFICIALAtualizada há 9 meses
- AWS OFICIALAtualizada há 2 anos
- AWS OFICIALAtualizada há 6 meses
But that won't work either , the users need to use snowflake-connector-python on the sagemaker studio notebook and the notebook will not be able to trigger the SSO with AWS Identity Cente either.
If the I execute the following in a SageMaker Studio notebook:
I will be presented with a prompt saying that snowflake-connector-python couldn't open a browser:
If I actually follow that process of copying (the really long URL) to my browser , the login process will complete on an error page http://localhost:xxxx/?token=xxxx if I copy that final URL onto the
Enter the URL the SSO URL redirected you to ____
then it will actually work.But the whole process it's not very user friendly
Can't you add some code catching this message, parsing the url and then sending a request to this url? (It's not ideal, I agree but it may at least provide at least a better user experience