I've added a custom profile attribute via the Okta admin screen called ABC_permissions. This string value has a Json payload which is almost 1Meg in size.
When I call the API via the full url in a browser https......./users/test1#axxx.com I see the profile with the custom attribute listed in the browser.
Unfortunately, using the c# SDK, the profile object shows zero unmapped attributes so I am unable to retrieve the json payload on the server side code. Any thoughts of what could be creating this issue?
This is a current issue with the C# SDK. Hopefully they will fix it soon.
Until then, you can call the API directly to get the user's entire profile, with all its custom attributes.
Related
We have web and desktop app. In both, we:
Get access token
Display Google Document Picker
Call Spreadsheets.get API to get selected document (https://sheets.googleapis.com/v4/spreadsheets/<document-id>?includeGridData=true)
For the desktop app, Spreadsheets.get API returns 404.
At the same time, for web version it returns document contents, as expected.
And after document is imported in web version, import in the desktop app (of the same document) is not failing anymore.
The code for fetching a document is common for both applications.
The difference is in getting security token.
For web version, token is obtained using JS Google API (gapi.auth2.authorize method), and desktop auth is based on https://accounts.google.com/o/oauth2/v2/auth page.
On every import attempt the new token is being obtained.
Scope: https://www.googleapis.com/auth/drive.file
Does anyone have any idea what may be the cause?
Resolved.
I simply forgot to specify app id for the Document Picker in the desktop app 🤦♂️
I am using yammer REST API to get group data in sharepoint from yammer, it is opening a new tab for authentication. Is there any way to prevent this new tab?
I tried to open yammer in a hidden iframe, which gives me error - "Refused to display in a frame because it set 'X-Frame-Options' to 'sameorigin'."
It sounds like you're using the JS SDK to make REST API calls. It needs a way to authenticate those calls so if it doesn't have an OAuth token to use from another source, it prompts you to login. Take a look at this blog post that describes how to preauthorize the JS SDK so you can start making API calls scoped to the user loading the page without requiring any interaction from the user.
https://blogs.technet.microsoft.com/askyammer/2016/11/04/preauthorizing-the-yammer-js-sdk/
How do I lower the requested access level of an existing google project?
It's currently asking for:
View your email address
View your basic profile info
Manage your contacts
When all I really want is to authenticate a user for login purposes, and I think all I need for that is:
Have offline access
One of the parameters you are passing when you create a credential is called scope, and contains a list of each of the services your users must authorize.
From the OAuth 2.0 docs, scope contains a string or iterable of strings. Change it to the new scopes you want.
I'm assisting another developer with adding a link to a page in a product called Lawson that we use in-house. I need to pass the authenticated user's employee ID to an HTML page we're bolting on. I'm still looking at existing pages on the server, but thought I'd ask: does anyone know how the Javascript object that represents the authenticated user works? It looks like something server-side must be dynamically creating a Javascript object that has useful properties. It is usually called 'AuthUser'. I want to add the necessary JS references to my new page to support this object and access its properties. Does anyone have any experience with that? Thanks!
If you are in a portal session, you can access this in javascript through attributes of portalWnd.oUserProfile:
alert(portalWnd.oUserProfile.getAttribute("id"))
This will give you the logged in user's short username. Many other attributes are available. To see a complete list, log into a portal session and then replace the URL with:
http://YOURPORTALSERVER/servlet/Profile
I'm not sure what you mean by "bolting on", but if you want to pass an attribute to an external page launched from a Portal session, you could create a user shortcut via Portal preferences using something like:
javascript:window.open("http://yourserver/yourpage.html?user=" + portalWnd.oUserProfile.getAttribute("id"))
as the target and process in yourpage.html like a normal GET method form.
If you are still puzzling over this all these months later, provide some specifics if you need more guidance.
I am trying to use Google places api to search the location. But Unfortunately I am getting only 1 message in responce is REQUEST DENIED. I have created new API key, but the API ACCESS Menu shows some warning icons as shown in below image does it created any issues or any other issues belonging to API key ?
Please let me know how to overcome this issue.... thanks in advance!`
my request string is this
You should also never post your API Key on the Internet like in your request string above to prevent your key from being abused. Your API Key should be kept private like a password as any usage of your key will be logged against your account.
The request above works fine using my API Key, I would suggest generating another API Key on the API Access page of the APIs console. Also make sure that you have enabled the Places API under services, instructions are here.
The notification icons are there to notify you that you have not enabled billing on your account yet.
i have the same error. the error was resolved by append &sensor=false at the end of API
I've had this issue, turns out using the key for Android applications (the one used for the maps API) is wrong. I needed to create a key for browser applications. Once I used the browser key instead of the Android key everything worked fine.