I have a problem when trying to connect to my teams account via my navigator (I tried chrome, firfox and Microsoft Edge).
I usually get this error after providing login & password:
Related
I created an SPFX application with the Teams Toolkit that utilises Microsoft Graph API to get data,after packaging and deploying the manifest folder to Teams Admin Center, it renders well with accounts that have Teams Admin and Global Admin access but accounts without this access are unable to access the application as it shows an error as seen in the image.
The Component ID and version in the message are speaking to the React-dom component id and version in the project.
Please i need suggestions on how to resolve this as i am not sure if its just a permission issue
I have tried updating my spfx version but that didnt work as i was already working with the required version of spfx and all other dependency versions
You can raise an issue in https://github.com/OfficeDev/TeamsFx/issues so we can support you better.
I tried to reproduce your issue but failed. The web part displays successfully for account without Teams/Global Admin in my side. Let's clarify the steps before the issue happens:
Create a SPFx project in Teams Toolkit and utilizes Microsoft
Graph API to get data
Click 'Provision in the cloud' to provision
the Teams app (with Teams/Global admin account)
Click 'Deploy to
the cloud' to generate the sppkg and deploy it to SharePoint (with
Teams/Global admin account)
Click 'Publish to Teams' to publish
the Teams app manifest in Teams app catalog (with Teams/Global admin
account)
Approve the submission in Teams admin portal
Install
and open the Teams App in Teams with Teams/Global admin account and
the web part displayed successfully
Install and open the Teams
App in Teams without Teams/Global admin account and the web part
shows error.
Could you help confirm whether you're having the steps above to reproduce the issue?
BTW, after deploying you should be able to use the web part with normal account in regular page in SharePoint. Maybe you can check whether everything is OK in SharePoint app catalog
SPFx solution after deploy to SP app catalog
I created a virtual assistant with the ITSM skill attached with Token Authentication enabled and the bot runs well when using direct line through a browser.
Next, I added it into Teams and after a bit of troubleshooting, I got it working. I authenticatee and could interact with the VA and the Skill. The next day however, I was unable to get the bot to prompt for authentication and by then my token authentication had expired. Next, to verify I have a fix for this issue, I found if I completely cleared my MS Teams cache and my browser directories via the url below, my authentication request prompted this time and I was again able to login and the bot worked correctly. So my question is, what causes the token in teams to not be able to reprompt, can this be fixed and or is the right way to do authentication in Teams to use a Single Sign On solution and if so how does one do that in Teams with a Virtual Assistant from the botframework?
https://commsverse.blog/2018/09/28/clear-the-microsoft-teams-client-cache/
When I try to connect to Dynamics 365 CRM with the Plugin Registration Tool I get the following permission error:
"You don't have permission to access any of the organizations in the
Microsoft Common Data Service region that you specified. If you're not
sure which region your organization resides in, choose "Don't know"
for the CDS region and try again. Otherwise check with your CDS
administrator. Parameter name: EMEA"
I have the System Administrator role
I can sign-in to the web interface and work with no issues
I'm sure of our region, tried to login with and without it ("Don't know" option)
Also tried with an application password as our organization uses multi factor authentication
Using the latest version of the tool on Nuget (9.0.0.9506 in the about dialog)
I can connect to my trial server the same way
We had a user who was able to connect with the same user roles set
This seems machine and account independent. Other users including the organization creator are getting the same error
We are directly connected to the internet, no proxies
One solution I've read suggested cleaning the cache files which don't appear on my system. And we get the same error on clean installations.
Solved by leaving the "Show Advanced" checkbox unchecked and not entering User ID / Password. Then a second dialog opens for credentials and 2FA authentication which just works.
You don't need an application password, as you'll be asked for MFA in the next step.
I don't know how our old teammate was able to sign in with the "Show Advanced" option selected. He was getting the same dialog and continue.
In Internet Explorer, when I go to any site that is authenticated via Azure AD, the login page automatically chooses to log me in with my Windows Account. This functionality would typically be great, but I need to use different credentials (my clients).
How can tell IE to NOT automatically log me into Azure AD with my windows credentials?
When I use any different browser, the expected functionality exists and I am prompted to enter the login credentials I want. Also, the solution can not be "just use a different browser". Client uses IE for everything and won't allow users to install different browsers.
I am running Windows 10.
Thanks in advance
Opening IE InPrivate window should allow you to login with any user you need.
Use Ctrl+Shift+P or Settings Icon->Safety->InPrivate Browsing.
Is it possible to have automatic user authentication from Active Directory when open Internet Explorer without user enter username/password.
As right now. I have windows authentication, where users after open internet explorer, they have to enter he/she username and password from AD. So since the application has the same credential that the PC. I was wondering, how could i do so user don't have to log in when open internet explorer to use the web application.
I am thinking something like single sign on type of deal.
If your users already log in with their AD credentials your problem is almost resolved.
Your users have to add the site to the local intranet zone (so they aren't prompted for credentials) in their Interner Explorer Configuration. Also check in internet explorer security zone settigns that the following is enabled:
User Authentication -> Set Automating Logon Only In Intranet Zone