We have added the StreetAddress to Profile Card Properties as per the following command:
POST /beta/organization/{organizationId}/settings/profileCardProperties
and confirmed the setting with a corresponding GET, as described at
https://learn.microsoft.com/en-us/graph/api/organizationsettings-post-profilecardproperties?view=graph-rest-beta&tabs=http.
However, despite waiting many days, the Office 365 Profile Card is not showing the StreetAddress as a property. We have the values for StreetAddress populated in user profiles.
Could this be checked please, as we have different offices with similar floor numbers, so having the StreetAddress in the profile card is quite essential?
This might be the issue with permissions, have you tried to check the permissions you are using whether they are delegated or Application permissions.
This only works for delegated permissions:https://learn.microsoft.com/en-us/graph/api/organizationsettings-post-profilecardproperties?view=graph-rest-beta&tabs=http#permissions
Related
Based on LinkedIn Documentation:
The following selection of profile fields are available to all
LinkedIn developers:
Basic Profile Fields
Location Fields
Position Fields
However, when creating a LinkedIn OAuth app (https://www.linkedin.com/developers/apps), I only get access to Basic Profile Fields (through the r_liteprofile scope).
How do I enable access to Location and Position Fields (and what are the corresponding scopes)? My intention is to avoid having to request Partner Program membership as (1) I dont need as much info and (2) it takes a while to get approved.
Thanks in advance, Miguel.
This is my first time using of zendesk, and I am facing some problems here
I need to set the name, email and external identifier of user before start any activity to be shown in the tickets screen
here is my code
Identity user = new AnonymousIdentity.Builder().withEmailIdentifier(mEmail).withNameIdentifier(mName).withExternalIdentifier(mIdentifier).build();
ZendeskConfig.INSTANCE.setIdentity(user);
Intent intent = new Intent(ContactUsActivity.this, ContactZendeskActivity.class);
startActivity(intent);
no thing appear in my tickets screen only "Mobile App User", non of my information is shown
can anyone tell me what is the problem here ?
Full disclosure: I'm one of the SDK devs. Generally you end up seeing 'Mobile App User' because of the way that the user lookup works.
Before I start, I'd like to point out that withExternalIdentifier is optional. I'd only recommend using it if you know for sure that you'll always have a unique ID there.
If you give us an external ID, we'll try to see if a user exists in your system with that ID. If it does we use that. For security reasons we don't let a mobile identity update the user. If no match was found on the external ID, we then look at the email, and follow the same lookup process.
The only time where the external ID and name will be set is if you are creating a new user. New means one that wasn't found already with the external ID or email that you are supplying.
If you still have issues you can drop us an email to support#zendesk.com
Thanks!
I'm writing an ASP.NET MVC application, which uses the Membership database to store user registrations. I use email addresses as usernames. When a user registers in my app, I send out an email-confirmation to the address they have used during registration. i.e. I send out an email with a link, which the user is supposed to click, to verify that the address belongs to him.
Until that link is clicked, the account remains 'Unconfirmed' (i.e. EmailConfirmed column equals False). Which means, the account is created, just not active.
How do I deal with a hacker who brute-force creates accounts? I see two big problems here:
Ever-increasing size of the Membership database. A single user, from
a single computer is not a threat, but what if he has 'zombie'
computers?
If User1 creates account with User2#example.com email and
User2 ignores the activation email, the account will essentially
remain locked (unconfirmed), but existing. If User2 decides later to
actually create an account, they can't use their email to register
(account already exists) and they can't Reset Password either -
because even if they reset the password, that does not necessarily
Activate the account.
As for 2) I see a couple of options:
Set expiration date on unconfirmed accounts - i.e. allow the username/email to be claimed again, if the email is not confirmed with 24hrs
Modify my Reset Password method to also activate the account, if it has not been activated. Is that a good idea? I mean, the person would receive an email for that, which is essentially a confirmation, if they click the reset password link in it.
Anything else?
What about 1)? How do I protect myself against bulk create of accounts? Aside from limiting 1 account per IP, per day, using code.
One simple way to deal with this kind of problem is crude but effective.
I usually add an additional field to the form that doesn't form part of what I need - but has a legitmate sounding name like 'Company' - and then I hide it from screen view using CSS. Real user's will never see this on screen, but a bot crawling through the HTML will find it.
Then, when the form is submitted, first I check to see if that form field has a value. If it has - I stop the page from executing any further or just return an HTTP Error as in 99.9% of times only a bot would have filled out that field - not a real user.
//anti-bot measure
if (!String.IsNullOrEmpty(Company.Text))
{
HttpContext.Current.Response.StatusCode = 400;
HttpContext.Current.Response.Status = "400 Bad Request";
HttpContext.Current.Response.End();
}
//carry on processing the form...
I've been using this technique on forms for several years and it's been extremely effective!
I've authenticated user with MS Live oAuth2 api using "wl.basic,wl.birthday" scopes (which includes all the needed info as stated in http://msdn.microsoft.com/en-us/library/live/hh243646.aspx).
User has both gender and his birthday set on live.com user management page.
But when i'm trying to get user data with https://apis.live.net/v5.0/me?access_token=*, i get JSON where gender and birthday (birth_year, birth_month, birth_day) are always null.
Do i need some different scope? Or MS doesn't return them at all?
Could it be that data isn't populated somehow, because i use freshly created user?
I had this same problem. My birthday was set in my Live Profile "Account Settings" (accessed via the top-right user menu next to my avatar), but the three birthday values were null in the OAuth response.
On my Live Profile page (profile.live.com), I noticed links to my Skype and Messenger profiles. My birthday was already showing up in Skype, but not Messenger. When I set my birthday in Messenger, birth_year/birth_month/birth_day were populated in the OAuth response.
I have created a lookup field on my custom object to contact and it is used on visual force page. Also I have used custom lookup page.
In salesforce org it works fine and display lookup value. But when i use this page in sites then lookup value does not show for those contact which have no account.
If contact have account then it shown. I have already give permission to site users.
Contacts without accounts are Private Contacts, and can only be viewed by the record owner.
The solution is to create a special account record, I usually call it "Orphanage". Then relate these orphan contacts to that account.