How can you sign in to Palo Alto Global Protect when you have multiple Microsoft Profiles? - vpn

When I click "connect" in Global Protect 5.0.1, a message appears in the dialog:
Microsoft
Sign in
Sorry, but we’re having trouble with signing you in.
AADSTS50105: The signed in user 'xxx.xxx#otherdomain.com' is not assigned to a role for the application 'cc1a06de-b346-4e7e-b5fa-35b227c13063'(Palo Alto Networks - GlobalProtect).
Request Id: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx (redacted)
Correlation Id: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx (redacted)
Timestamp: yyyy-mm-ddTxx:xx:xxZ (redacted)
Message: AADSTS50105: The signed in user 'xxx.xxx#otherdomain.com' is not assigned to a role for the application 'cc1a06de-b346-4e7e-b5fa-35b227c13063'(Palo Alto Networks - GlobalProtect).
Advanced diagnostics: Enable
If you plan on getting support for an issue, turn this on and try to reproduce the error. This will collect additional information that will help to troubleshoot the issue.
Other information:
I have a Microsoft profile for "other domain".
I had uninstalled Internet Explorer 11 before installing Global Connect
Right clicking on the dialog indicates that the Internet Explorer 11 rendering engine is still being used for this dialog. A "Back" menu item is available, but has no effect. A "Properties" menu item is available and I can use the URL to log in to the NEW profile (e.g. in Chrome) but I am loath to re-install Internet Explorer 11 unless I really have to.

Related

my.telegram.org sends an ERROR when I want to create an API id/hash in API development tools section

I'm trying to get my API id/hash to create some bots for telegram , but in the API developmen tools section , when I enter my bot informations( name , shortname...) and click on create to get the results , I recieve an error :
my.telegram.org says ERROR
I live in Iran and telegram servers are blocked here .
Any solution for this problem?
!! I found the Iranians-only solution which I wrote down below .
I disable the "AdBlock" extension in the browser and it's work.
That may happen with enabled VPN extension as well
I've found a solution! ( works for people in Iran mostly , cause telegram servers are blocked in Iran , same as facebook and tweeter . so you can log in to telegram site but when it comes to telegram api , no data would be transfered because it's blocked . )
simple requirements : Android phone + VPN(proxy)
If there's any Android phone close to you, take it and install a vpn (or just use a proxy to change your ip) and try to do get your API id/hash.
If you have same problem again, just try other proxies or install other vpn apps. Surely you will get your API id, just be patient and repeat the process.
The ip address must be in the same country as the mobile phone number of the telegram account when applying
In my case the only way to make it work was to switch from Chrome to Safari
The ip address and phone number should be in the same country. If you are in countries that prevents you from Telegram such as China. The only way is to use the mobile number of another country (you can use Google Voice, textnow or etc.). By the way, if you use a +86 phone number, you can try using the IP address in Hong Kong
Working as of 1st January 2023
I've managed to register new App in PC under VPN (IP with another country that same with my registered number origin country) with following form details:
App title: TestApp1
Short name: testapp1
URL: N/A (Fill nothings here)
Platform: Desktop
Description: N/A (Fill nothings here)
OS: Windows 11
Browser: Microsoft Edge (InPrivate mode without any plugins installed)
Hope this helps!

Unable to link account in Device Access Console

I created project in device access console and established my OAuth. When I add my project and id into the script I receive the following error in the browser:
Can't link to NewHA
I am new to this - so any advise is appreciated
first when you make the first request:
redirect_uri=https://www.google.com&
access_type=offline&
prompt=consent&
client_id=oauth2-client-id&
response_type=code&
scope=https://www.googleapis.com/auth/sdm.service```
the `project_id` references to the sandbox project_id.
https://developers.google.com/nest/device-access/authorize?authuser=4#link_your_account
"Open the following link in a web browser, **replacing project-id with your Device Access Project ID** and oauth2-client-id with the OAuth2 Client ID from your GCP Credentials"
**another issue you may have** can happen from the account you used to open the device-access-Project. **it must be a private and not G suit account** (ending with #gmail.com and not #comapyName.com).
this is because the nest doesn't let you create a G Suit account (https://stackoverflow.com/questions/64074857/pcm-no-access-to-partner)
and you can't invite a private nest user to your google home while using the G suit user (as this isn't possible)-
https://support.google.com/googlenest/thread/426784?hl=en&msgid=560455
so even if you created the 'sandbox' with the G-suitaccount you can't use it to invite a private user (and will have to re open the account and pay again 5$)

Google AnalyticsAPI - This service is not available from your country

I have successfully integrated Google AnalyticsAPI few days ago.
Since monday I am receiving an 403 error, which returns "This service is not available from your country".
Production-Server details : Ditigal Ocean - Amsterdam - AMS3.
The strange thing is that my Google AnalyticsAPI integration still works properly in my test-server that have the same configuration of the production-server (Ditigal Ocean - Amsterdam - AMS3).
How can i solve it?
Thanks
Looks like an error, similar to the one described here
Google Contacts API responds with "countryBlock" error
A good place to start would be filling out the Developers Console feedback form that can be found next to "Help" button in the console toolbar.

Integrate twitter in drupal 7 website

I am trying to get the twitter module (7.x-5.4) running on my local drupal 7.19 website. Already installed Oauth and registered a twitter app. I am using the keys of that twitter app.
Callback URL
http://localhost/drupal-7.19/twitter/oauth
twitter host
http://twitter.com
Twitter API
https://api.twitter.com
Twitter search
http://search.twitter.com
TinyURL
http://tinyurl.com
when I want to add at least my own twitter account so that the site can display my tweets. when I want to add this account, an error occurs:
Notice: Undefined property: stdClass::$data in Twitter->request() (line 131 of root\modules\twitter\twitter.lib.php).
Could not obtain a valid token from the Twitter API. Please review the configuration.
any ideas? thanks in advance.
In my case, uncommenting the line
extension=php_openssl.dll
in php.ini resolved the error.
I'm not sure this will work for you, but this worked for me. I had the same exact error, even though I had followed the documentation. Here's the test: go to admin/reports/status. If you see the following warning: "HTTP request status Fails" this means your drupal/LAMP stack is unable to use DNS to callback to itself. In my case I used my machines's IP to access my Drupal instance. So, rather that use "localhost" use your machine's IP address (you can use ipconfig on MSWin or ifconfig on Mac/Linux) and use that for finishing the twitter account setup process.
Again, not
http://localhost/drupal-7.19/twitter/oauth
but
http://10.0.1.9/drupal-7.19/twitter/oauth
(substituting your machine's IP address)
I was getting the exact same error which i fixed by adding appropriate proxy server details.
Notice: Undefined property: stdClass::$data in Twitter->request() (line 131 of C:\wamp\www\test_twitter\sites\all\modules\twitter\twitter.lib.php
The problem was due to proxy-settings. I added values for $conf['proxy_server'] and $conf['proxy_port'] in settings.php and this error vanished.
I also verified that if i remove the proxy settings, this error is reproduced again.
Install oauth_common and twitter on your Drupal site
Check that both Oauth and the Twitter modules are enabled. I didn't use any of the other Twitter modules to do this
Go to the twitter module in Drupal
Go to the Configure (button) -> settings (Tab)
(note that the Callback URL is http://localhost/yourwebsite/twitter/oauth i.e. it doesn’t have to be 127.0.0.1)
Click on the link that says register your application
Go to twitter and sign in to be a developer
Add a new application, making a distinct feed name
Enter your site details
For localhost use: http://127.0.0.1:8000/twitter/oauth for both the website and callback URLs
Press save when you've done
Next go to the Test OAuth button - this will give you your illusive consumer key and consumer secret key
Back to the Drupal website and and to the twitter module to configure (button) -> settings (Tab)
Copy and paste these consumer and consumer secret keys you just got
Press Save configuration
Hopefully no errors.
Go to the twitter tab in the module and hopefully your twitter avatar has appeared
Read the top of the page where it says "Tweets are pulled from Twitter by running cron. You can view the full list of tweets at the Tweets view."
Select the View Tweets checkbox and click view - Chances are your tweets won’t show up in the next window - yet
Go to your drupal Configuration screen and to [System] Cron and press the "Run cron"
Now go back to view tweets from the twitter module and they should all appear
[This was a pig to figure out]

Published asp.net WebApp won't connect. 401.1 unauthorized

asp.net app (c#) worked fine in debug mode; published, getting 401.1 error (unauthorized).
When I put in the url, a dialog asks for username & password. Put it in 3x, error.
It's an internal app, using Windows authentication only.
IIS 7.5, using ApplicationPoolIdentity.
SQLServer Database
Specific Error Message from 401.1 page:
Module WindowsAuthenticationModule
Notification AuthenticateRequest
Handler ExtensionlessUrlHandler-Integrated-4.0
Error Code 0x8009030e
Requested URL http://smalltools.dbsvc.com:80/ Ap
Physical Path C:\inetpub\SmallTools
Logon Method Not yet determined
Logon User Not yet determined
The app has a users table to determine the "role" of that user. I put a method in the master page that queries the table based on authenticated user, and returns the role. This, in turns, determines which buttons are visible on the navigation bar.
Looked in the security log, and found the following 3 entries:
2012-07-20 14:55:11 10.0.1.38 GET / - 80 - 10.0.13.106 Mozilla/5.0+(Windows+NT+6.1;+rv:14.0)+Gecko/20100101+Firefox/14.0.1 401 2 5 15
2012-07-20 14:55:20 10.0.1.38 GET / - 80 DE\cin.bro 10.0.13.106 Mozilla/5.0+(Windows+NT+6.1;+rv:14.0)+Gecko/20100101+Firefox/14.0.1 500 0 0 125
2012-07-20 14:55:20 10.0.1.38 GET /favicon.ico - 80 DE\cin.bro 10.0.13.106 Mozilla/5.0+(Windows+NT+6.1;+rv:14.0)+Gecko/20100101+Firefox/14.0.1 404 0 2 0
Any idea what might be causing the inability to log in? Any clues what I can fix to make it work? I've researched all day and haven't found what might be the problem.
Any information is gratefully received.
Thanks
Cindy
I've successfully solved the issue; I had to allow impersonation, and make an adjustment to the AD group.
The article in the following link helped a great deal:
http://msdn.microsoft.com/en-us/library/bsz5788z.aspx
If this is an external site, then Windows authentication isn't really the way to go. But you can still do it, here's some links I found that should help.
Q&A about similar issue
Microsoft guide on how to implement
Typically Windows Authentication is used with internal systems because the users are logged on directly to the system and all their credentials are right there. However for external apps this isn't always the case, since your home Windows account and work windows account aren't the same, in addition you may not even be using windows from the external location.
Another gotcha I came across is the local loopback address security check when you setup a DEV instance and modify hosts file to use Fully Qualified Domain Name (FQDN) or simply when you browse IIS site with custom headers and the name does not match the server hostname. While this is necessary for production servers it is a problem when setting up Developer environments.
"This issue occurs when the Web site uses Integrated Authentication and has a name that is mapped to the local loopback address"
There are two main methods to resolve the issue:
Specify host names (Preferred method if NTLM authentication is desired) by creating/updating the Multi-String value:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0
Disable the loopback check (less-recommended method - do not use on production servers) by setting the following registry DWORD value to 1
HKLM\SYSTEM\CurrentControlSet\Control\Lsa\DisableLoopbackCheck
Please refer to this HTTP 401.1 - Unauthorized: Logon Failed - Microsoft Support article for detailed overview and registry settings.

Resources