Hey Sonny - adding hide_title=true should work in SSO embed dashboards. Feel free to visit help.looker.com or come on chat if you are still having issues, and we can troubleshoot it with you!
Hey @srivera1
Thanks for help!
Actually we have already code in C# for sso embedding of various looker objects(looks, dashboard), and are using in our application.
But we are also looking to use all_dashboards() and other sdk API’s to get all available dashboard and their related metadata into our application programmatically from Looker.
I’m currently developing a .NET C# SDK for looker. I’m very interested in the API and new features coming with the API. Let’s stay connected and make sure this train keeps rolling.
Thanks
Can this document be updated to include documentation for the group_ids parameter introduced here:
Hi all, is it possible to specify different connection models for user-defined dashboards/looks when embedding them with SSO url approach?
@Alexander_Karta As today dashboard’s are distinct per model, and models are distinct per connection. We’re building out a feature in 4.4 called user attributes which would allow you to dictate connections per user, however I may be misunderstanding your issue, and in that case user attributes would not help.
If you’re curious if you’re able to point a dashboard to a different model in the url, that is not possible. If you’re curious about pointing a model to a different connection per user, and using that model for the dashboard, that would be possible in 4.4 (see above comment).
Happy to talk use cases if you wouldn’t mind expanding on it.
@Zam thanks for the answer, I’m looking for something like described in this article for LookML dashboards but for user-defined dashboards/looks:
https://do.main.com/login/embed//embed/sso/dashboards/model_name_here/dashboard_name_here?...
where I can specify connection model and if I understood correctly from your comment it is not possible?
@Alexander_Karta It’s not possible for user-defined dashboards, as they’re are not linked to a specific model. Looks as well are objects with saved queries to them, in which they will belong to a model.
The only options you have for adjusting models via the url are with LookML dashboards and the explore page. These options due however rely on the caveat that either the LookML dashboard or the explore path do exist in the model you’re switching to. An example of what the url would look like for a model,
https://do.main.com/login/embed//embed/sso/explore/model_name_here/explore_name_here?...
Hi @All,
We are trying to generate the Embed URI for using dashboards embedding in our Salesforce. We are using Salesforce(APEX) code for generating the Encoded URI.
But, when we use the URI in the Embed URI Validator we are recieving the following errors:
- ‘signature’ param failed to authenticate
- ‘time’ param is not within 5 minutes of the server’s system time .
The latter one, we were able to resolve the error but for the prior we were not able to resolve. Even we tried to make use of online signature encoder for encoding the signature param.
Please note : we are not passing any model param for embed uri
Please help and guide us if we are missing anything.
Thanks.
Hey @vishals
Would you mind visiting help.looker.com so we can take a closer look at your code and the URI it’s generating?
Thanks!
Hi Brad, we are developing the apex code for the same but we are getting error "‘signature’ param failed to authenticate: ". Can you please help as you have already done that!! Thanks.
Hi @All!
We are trying to embed looker on our site and it seems like we reached the URL length limit.
We have a long URL to an explore page with a lot of parameters such as fields, vis, filter options and so on. The URL with embedding parameters is really long as a result.
Ability to change connection in the URL is important criteria for us. This is why we use explore screen this way.
Could you give any advice what can we do in this situation? Maybe we can decrease the length by replacing some options with shortening ones, creating some aliases for a group of parameters in Looker or something else? Or maybe we can extend the max URL length in the Looker configuration or so on?
Any idea would be great for us.
Also, could you please tell what the max length of a URL is?
Hi @sani
Could you please provide us with more details on how are you trying to change the connection using the URL?
I can see that some browsers/servers have problems with URLs over 2K characters.
Could please you tell me the length of your URL? you can email us to help.looker.com
Best,
Sara
Hello @Sara_Guzman ,
We are going to change the connection this way:
https://looker.ourDomain.com:9999/login/embed//embed/explore/first_connection_model/client?fields=…
https://looker.ourDomain.com:9999/login/embed//embed/explore/second_connection_model/client?fields=…
Original Looker URL contains about 1990 characters. The final URL with embedding parameters contains more than 3412 characters. (I used encoded URL for calculation)
Using the url we can change the model, but we cannot change the connection. In order to dynamically change your connection, you can use the user attributes in the Additional Params field, of the Connections page in the Admin section of Looker, as shown in this Doc.
Additionally you could have multiple models that all extend a base model, but have different connections in their model file. Please let me know if this helps.
Best,
Sara
Hello @Sara_Guzman ,
Thank you for the information but I still don’t understand how this can decrease the length of the Explore URL which we need to embed on our website. The “Explore” URL length is the main our problem.
Is it possible to use a short link or compress parameters in another way?
Sara_Guzman:
Doc
Hi @sani
It is possible to shorten the URL. Could you please visit us at help.looker.com or come to our chat support? There is more info and details we need in order to address this.
Best,
Sara
Hi,
I have been trying to implement SSO Embeding following the instructions step by step and I was getting “‘signature’ param failed to authenticate:”.
After a lot of playing around I figured out that the reason for that, was because when trying to generate the signature I was using the embed URL by its strict definition (e.g /embed/dashboards/1). However this is wrong.
What needs to be used in order to generate the signature in the above case should be the path plus the encoded embed URL (e.g /login/embed/%2Fembed%2Fdashboards%2F1)
I believe the instructions on thepage are misleading, since it’s stated that for generating the signature, the second parameter after Host should be Embed URL which is defined earlier in the page just as just the path after /login/embed/.
I hope this helpful for anyone who was confused like me.
1 Like
You’re right, by George! (sorry, bad joke).
I think you’re actually right, though— This is something we should clarify.
In all of our example scripts, we specify the un-encoded URL in the url_params, so that when the actual URL is created, it can all be encoded at once. During the signature generation, we do encode just the embed url before generating the signature.
I’ll check in with the docs team about this. Thanks!
@gpaparisteidis , confirmed that we’ll want to add that in— I sent over a request to the docs team. Thanks for the eagle eyes! Glad you figured it out.