I have created a dashboard using aws quicksight. Now, I want to embed it into a web portal. My requirements are -
I want to show these dashboards only to specific users among all the people who access our web portal.
Currently, that user list is fixed. But, if I want to give permissions to any new user, I want to be know the different ways to do that
Can someone tell me embedding process in detail ? I have went through these aws quicksight resources about embedding - 1. link 2. link. But, I am finding it difficult to understand about the access management part and retrieving the dashboard URL part. I am using javascript.
Related
I am researching ServiceNow, I know next to nothing about it. Funny how the most obvious questions seem to be the hardest to Google. My specific question is about applications.
ServiceNow runs as SaaS, correct? So, if I build a ServiceNow application, for a user to access that application, they would open the ServiceNow platform in their browser, then they would have a menu of applications they could launch, correct?
Is it possible to host a ServiceNow application on a specific page, or on a website, or embed it in a SharePoint page, so I can give out a URL for a user to run the application? Or do they always have to navigate through the ServiceNow portal to run my application?
I know this sounds like a dumb question. But everything I have read assumes you already know this information, so a dumb, obvious question it has to be.
ServiceNow assumes that it is managing the entire window (or tab). You might be able to get something to work using HTML frames, but there is a good chance it would break with a future ServiceNow upgrade.
On the other hand, it possible to redirect a user into a specific ServiceNow page by constructing the appropriate URL. If the user does not already have an active session cookie then ServiceNow will prompt them to authenticate. You can redirect to a specific Service Portal page, or a specific catalog item or a specific record. You can redirect to a ServiceNow Dashboard. If you want to show a list of records, you can dynamically build a query. You can redirect into Agent Workspace or the classic platform UI. If directing into the classic platform UI you can show or hide the ServiceNow navigation menu based on whether or not your URL contains nav_to.do?.
There is a bit of an introduction on this page, although it really only scratches the surface:
https://docs.servicenow.com/bundle/sandiego-platform-user-interface/page/use/navigation/reference/r_NavigatingByURLExamples.html
If you want to drive ServiceNow from a web site or from SharePoint, then you just need to construct the right URL which will open ServiceNow in a new browser tab.
I'm working on a Laravel site where users could connect their Google account and manage their Google calendars directly from within the site. I found https://github.com/spatie/laravel-google-calendar but I'm not sure that it really meets my needs.
That package doesn't seem to follow the authentication flow (OAuth 2) I'm used to with other APIs. It uses service accounts and stores credentials in JSON files where I usually save access and refresh tokens in my users table.
So am I missing something or is that package not made for that kind of site ?
I received this message for the second time and i still dont understand why. Can someone help me?
Action required: Critical problem with your Google Cloud/API project
Youtube API (id: tonal-topic-123301)
Dear Developer, We have recently
detected that your Google Cloud/API project Youtube API (id:
tonal-topic-123301) is using a Google product name as the project name
shown to users on the OAuth consent screen, which violates the Google
API Services: User Data Policy. You can fix the problem by revising
the project name and other relevant content so that the OAuth consent
screen shown to users accurately reflects the identity of your
application. To revise the project name visible to users, please take
the following steps:
Please review the Google API Services: User Data Policy, specifically
the following section- "Do not make false or misleading statements
about any entities that have allegedly authorized or managed your
application. You must accurately represent the company, organization,
or other authority that manages your application. Making false
representations about client credentials to Google or Google users is
grounds for suspension."
Sign in to the Google Cloud Platform Console.
Select your project.
On the Home Page Dashboard, select Go to APIs overview under APIs.
In API manager, select Credentials on the left bar, then select OAuth
consent screen. Change the name in the field under Product name shown
to users and then click on Save. We will suspend your Cloud project in
3 days unless you correct the problem. Please submit an appeal if you
have any questions. Please note that you should be logged in as the
project owner to access the appeals page. For more help on submitting
an appeal or to learn more about the process check the Policy
Violation FAQ. Please take a moment to review the Google API Services:
User Data Policy, the Google API Terms of Service, the Google Cloud
Terms of Service and the applicable Terms of Service for the specific
Google API you are using so that you do not violate our terms and
policies in the future.
This is obviously a naming issue regarding something in the google product range.
You Should be able to re-name your project to solve this.
If not, try a Google forum or help pages.
The problem you are having is that Google does not allow you to use a Google product name as the name of your in your application. Users can become confused and assume your third party application was created by them.
How to fix it:
Go to Google Developer console find the credentials screen. Click on the Oauth consent screen tab at the top rename your application.
Note: If you don't do this google is going to shut down your application they are very picky about this.
How can i create a role for a user to access only dashboard tab to monitoring the graphs in kibana4 using shield?
The role must satisfy the below conditions
-The role must not have access to Discover tab,Visualize Tab and Settings tab.
-The role must have access to dashboard tab only.
Is this possible in Kibana4 with shield
According to this article, it is not currently possible with Shield:
Kibana and Shield do not currently provide a way to control which users can load which dashboards.
There is the issue #4453 that you might want to follow, if you're interested in how they will be solving this (and you can +1 it, too)
You can still protect your dashboard using either Apache or Nginx. See this discussion and this one.
Dynamics CRM (relative) newbie here.
I have an activity feed set up on a users dashboard (I used the Personal Wall web resource). If I look at the default posts for the Account view, everything is cool.
However, if I go and "follow" an Account when I look at my activity feed I can see other posts that relate to records that Account is involved with that are outside of my security role. For example, that Account has several Case records. My role has no permissions to Cases whatsoever, but there is the post in my activity feed. If I click on the case I get a prvReadPriviledge error which is correct, but I don't want users to do this - I don't want these posts to show up in their feeds at all, even if the are following the account.
These posts do need to show up in the feeds for people working Cases, however (and their roles will have read/write to the Case entity).
I'm not sure what do here.. can you help?
I believe that this is what you're looking for it's from Microsoft's site.
"The activity feeds walls are web resources that can be embedded in dashboards in context with relevant grids and visualizations. For example, you can embed the msdyn_/PersonalWall.htm web resource into a dashboard with specifying the HideUserProfile parameter. The default is value 1 (or, true), to hide the user profile, to unhide, use the value 0 (or, false). For more information about how to use web resources in dashboards, see Analyze data with dashboards."