We have some users with more than one network on yammer, we only have abc.com as company network and many users have private networks(itpor, o365).
We have built app for company users to query items with certain tags and display in gridview but it fails if some users are on different than private network.
Is there a way to set default network for Yammer REST call that only query company network even though user are currently on different network?
Related
We enabled guest access in our tenant as per https://learn.microsoft.com/en-us/microsoftteams/guest-access-checklist. We invited User-A who is another tenant using invitation API (https://learn.microsoft.com/en-us/graph/api/invitation-post?view=graph-rest-beta&tabs=http) as a guest. User-A accepts the invite and he\she is part of our Tenant but the Fast Tenant Switch is not showing for that User immediately. It is showing nearly after 24 hours.
1 . Is that usual behavior for Guest User or anything missed on the setup and\or in the invitation process.
We have an application that uses a couple different Google APIs (Login, Classroom). We originally wrote end-to-end tests to make sure that these integrations worked on a very basic level. Unfortunately, it looks like our end-to-end tests have started failing because Google is detecting "suspicious" login activity from the Google accounts we created to do the integration testing and is presenting Captcha's etc..
Is there anyway to get Google to whitelist an account so that they don't run it through all their security checks? We literally only use these accounts for automated testing.
As much as Email whitelisting goes this is what I found from the docs
Email whitelist:
An email whitelist is a list of IP addresses from which your users
expect to receive legitimate mail. When you add an IP address to your
email whitelist, mails sent from this IP address will generally not be
marked spam. To instead approve specific senders based on their email
address or domain name, create an approved sender list using the Spam
setting.
Please note that email whitelist is not exclusive. If you create a
whitelist for your G Suite account, it will affect your entire domain.
There's currently no functionality in place for you or your users to
only receive mail from a self-defined list of senders.
After you configure an advanced Gmail setting, it may take up to one
hour for that configuration to propagate to individual user accounts.
You can track prior changes under Admin console audit log.
To add IP addresses to your email whitelist:
Sign in to the Google Admin console. From the dashboard, go to Apps >
G Suite > Gmail > Advanced settings. In the Organizations section,
highlight your domain. In the Email whitelist section, enter the IP
addresses of your contact's domain host to make sure any mail
originating from these IP addresses are not labeled spam. If you would
like to add more than one IP address, enter an IP range in CIDR
notation or separate each IP address with a comma. Click Save changes.
I have 2 google adsense accounts. I plan to create one more. I want to be safe and login to every account from different IP's. I don't want to use public proxies because they can have bad history. What could be solution?
You can access every account from diff IPs by using TOR. Check it out: https://www.torproject.org/
Our developers have recently built a new internal 'image viewer' application for our staff to use. The image viewer runs as a website and uses Active Directory to authenticate the user and control what type of images that user is allowed to view.
I have this setup and working fine by running the website as an impersonated domain user. The problem I now face is that all the images are held on a non-domain share. How can I access this share using the domain user? The share is on a Novell Netware 6.5 server.
Alternatively I can run the website as a non-domain user and connect to the Netware server to retrieve the images, but then I am unable to query Active Directory.
Can I allow a non-domain user access to query AD? I don't wish to allow anonymous queries on my domain controllers.
No, a non-domain user cannot query Active Directory unless you configure your domain to allow anonymous queries.
Depending on how everything is setup in the web application, you may be able to insert some code to switch security contexts and impersonate a domain user at the point where the query happens.
Corporate networks use AD mostly to authenticate users - in that desktop machines require signing in to a Windows domain - which is centrally managed/universal.
Now, if I had an iPad and I brought it into work, I wanted to be able to sign in to my AD so that if I type http://internal.link into my iPad browser, it would resolve just like it would on a Windows desktop machine inside that corporate network.
To do this, I presume that the iPad will discover the company wifi network, and I would like to sign in to that wifi using my corporate AD credentials. This leads me to my questions:
How can a wifi network tie itself to Active Directory, granting sessions only to properly authenticated AD users? Do I need to purchase particular wifi routers or do anything specific on the AD side?
If I was to sign in successfully somehow using my AD credentials, I will then have use of the company wifi - with accompanying access privileges to resolve internal-only URL's. What would it then take to get my iPad browser to enjoy features that are available to corporate IE users such as SSO (seamless sign on)? At worst, would an application at http://internal.link simply prompt me to sign in again with my AD credentials?
You're talking about two different technologies here:
AD is used to identify individual users on the network. It's for authentication and authorization.
DNS is used to resolve the hostnames of internal applications. I.E.: http://internal.link resolves to 10.0.0.5
With that said, your work probably has some sort of wireless authentication mechanism. I've never heard of them using AD for that, but I suppose it's possible. You need to get on the work's wifi. Once there, your IPad will either pick up it's DNS server settings from the network via DHCP, or you will have to manually configure them (most wifi networks use DHCP these days).
Assuming you are successful in getting on the Wi-Fi, and assuming that your DNS servers are established (via DHCP or otherwise), you should be able to hit any internal site from the iPad as long as the wifi network has access to those internal sites. There are various reasons that it wouldn't (i.e. firewalls, etc.). The internal site, if it's using AD/NTLM will ask you for credentials when you first visit it. You can usually just supply your AD username and password, and it will work fine.
I would ask your sys admin, he/she will tell you in a second. Even though it is set up with AD and that is rather common their are many possibilities for set up and it is most likely not set up over wireless.