After I installed "Docusign for Salesforce Essential" in my org. I did navigate to "Docusign Setup" Tab. When I tried to click "Login with docusign", I got error that you need to setup your domain. After I did setup my domain. Now Everytime I go to "Docusign Setup" tab, it redirects me to login page and when i login it says "Page Setup doesn't exist". Has Anyone got this type of error?
Yes, it sometimes happens when you installed DocuSign before creating your custom domain. Uninstall the app and reinstall and follow the installation path again the error shouldn't appear.
Related
The problem: I'm getting errors from Google while attempting SSO through Azure AD and can't even begin to guess why or how to go about debugging the issue.
The story:
My org is looking at leveraging Microsoft's nonprofit benefits by setting up Azure for web hosting and Sharepoint to start with, which also entails using Active Directory. As it stands right now, we've successfully gotten our website running and accessible to the world on our custom domain, and our AD is populated with a copy of what's in our Google Workspace directory so we can use Active Directory as our authoritative directory.
We've been trying to implement SSO with the Azure/Gsuite connector, to have them auth with their Azure credentials to get into GMail, Docs, Drive, etc, but Google Workspace seems to choke. I have gone over the setup instructions repeatedly, ensured we're using all of the proper URLs in the Connector's SAML settings and in Workspace's "SSO with third party IDPs" settings, the proper certificate is in place... Provisioning is set up but not active, and I have successfully provision-on-demanded my account and an unprivileged test account.
Here are my settings in Azure:
Here are my settings in Google:
And to test this here's what I've done:
I open up a fresh InPrivate/Incognito window.
I go to https://myapplications.microsoft.com/ and am prompted to login. I use my unprivileged test account credentials.
Upon auth I click on the Connector app to attempt to go to my Gmail inbox.
After a wait on a white screen, I get a Google error screen with "Invalid Email - We are unable to process your request at this time, please try again later."
If I disable the SSO settings for my org in Google Admin, I'm able to log into the account just fine with Google, get to the gmail inbox, etc.
Conversely, if I attempt the same steps with my admin account, I get a similar page with a slightly different message, "Server Error - We are unable to process your request at this time, please try again later."
I have been bashing my head against this for two whole nights and can't make any headway. What gives? I can't even figure out how to debug these errors.
Somebody (me) failed their perception check repeatedly because the problem was that the Unique User Identifier SAML claim in Azure was set to user.mail instead of user.userprincipalname as it should have been as per the tutorial.
I'll see myself out now.
I am using Blazor WebServer with Identity Server template, downloaded from ABP.IO
When run locally, it all works fine. Login is success and able to see the post login page.
Once deployed to Azure App Service, Identity page shows correctly and even able to login. On the Blazor page, click on login, enter credentials, redirects back to the logged out page, but seems session is created, and login button shown. there is no error logged in the log files and console also has no errors.
Redis is running as Azure Redis Cache and there are no reported errors. I have deployed to below URL on Azure using the default template. Nothing confidential so I can share. The credentials are also the default credentials for abp.io.
Blazor: https://shoutout-core-dev.azurewebsites.net/
Identity: https://shoutout-identity-dev.azurewebsites.net/
It seems that there is no error already. Because when I make a request via swagger, I can access the necessary user information. As you stated, actually the session was created.
But there is a problem with the UI. To test the problem, after publishing the application in your local, can you run ASPNETCORE_ENVIRONMENT with the Production environment variable?
In addition, we need your ABP version information and your steps while publishing in local so that we can repeat the error.
this problem probably occurs on chrome. If you try to use firefox, you will pass the problem.Also, you can check this link for the fix on the chrome :
https://community.abp.io/posts/patch-for-chrome-login-issue-identityserver4-samesite-cookie-problem-weypwp3n
I am developing an ASP.NET MVC website. It is hosted in Azure and users are authenticated with AAD for our single tenant. I intend to make the website available in a Teams app, so that my coworkers can navigate to my website via the Teams Windows app and the mobile app.
I follow these steps to integrate security in a web browser: https://learn.microsoft.com/en-us/learn/modules/msgraph-build-aspnetmvc-apps/5-exercise-add-auth
I followed these directions to integrate security with Teams: https://learn.microsoft.com/en-us/microsoftteams/platform/tabs/how-to/authentication/auth-aad-sso. I'm not sure that I did this correctly.
At this point, I can:
Login with a web browser
Login via Teams mobile app
Load Teams in a web browser then load my app (not a use case that I need to support, but this worked and I was not prompted to login. I assume that I wasn't prompted to login because I was already logged in directly in another browser tab).
I cannot:
Login via Teams Windows app -- This is my primary use case unfortunately.
When I try to login with the Teams application on Windows (using the same pages and forms as on mobile), the page just disappears. I'm not prompted with the usual Microsoft login page.
How can I diagnose the cause of the problem? I don't see any obvious errors reported in Teams. Is there any way to get access to the root error?
EDIT:
login.microsoftonline.com is reporting "Your browser is currently set to block cookies. You need to allow cookies to use this service." I'm now aware of the SameSite changes (https://learn.microsoft.com/en-us/azure/active-directory/develop/howto-handle-samesite-cookie-changes-chrome-browser?tabs=dotnet) and I've implemented the recommended SameSiteCookieManager code to address the SameSite issue.
I'm still running into the same issue. No exceptions or errors reported except that Teams does not accept cookies.
May have to break this down further, here's how I would decipher it.
First of all, you will have to figure out if the issue is with Teams or on the Auth side.
Figure out which line of code is executing last? You can debug or write to terminal/logs.
Do you see any exceptions? Ideally debuggers can help or you can add some code to catch any exception.
If it's failing before executing any code, do you see any http requests going out, you can use fiddler for this. See if you are seeing any error codes.
If you are using Windows then check Event Logs for any errors or exceptions for Teams App. Look at the Application logs.
Look out for Audit logs and sign in logs and check if you see any activity in your tenant when you run this app.
https://learn.microsoft.com/en-us/azure/active-directory/reports-monitoring/concept-activity-logs-azure-monitor
Some other points would be to check if you can repro this with a sample app or a different user(elevated user). If there is any additional info do share.
I have created a YouTube API key, but when I try to use it I get an error message that the key is not enabled. When I try to enable the key in the Google Cloud Console, I get the error message:
IAM: you have insufficient permissions to enable or disable services
and APIs for this project. Contact a project owner to request
permissions.
I can't seem to find a way to set the project owner. I created this project myself, so I should be the project owner. I'm not sure if it's relevant, but the account is managed via G-Suite.
Update: per the documentation, I logged on to G-Suite as an administrator and went to Apps > Additional Google services, but "Web & App Activity" is not listed as an option.
Your gsuite admin can activate the API or remove a restriction on it.
To add an owner for a project, first select the project in the dropdown at the top of the screen. Then go to "IAM and Admin" in the navigation bar, then go to the IAM page. Click on "Add" at the top, and then you can add Project->Owner.
It can be confusing because even if somebody is an organization administrator, they aren't necessarily the owner of a project yet.
I'm in the process of migrating a Google App Engine / Java based app over to the new Google Apps Marketplace.
The old app enabled users to install the app without actually being on the marketplace page by leveraging a redirect URL extracted from a user click on the "Add It Now" button from the old marketplace page. This URL triggers an account login button that is then followed up by the app install. The URL was of the form:
https://accounts.google.com/AccountChooser?continue=https://www.google.com/enterprise/marketplace/interstitialRedirect?domain&productListingId=&index=0&followup=https://www.google.com/enterprise/marketplace/interstitialRedirect?domain&productListingId=&index=0&service=marketplace&passive=true&ul=1
I've tried using the redirect URL generated from clicking on "Integrate with Google" from the new marketplace page but it goes through the authorization page then leads me to a blank page (though the app is successfully installed). The blank page issue is likely related to the following issue - Chrome Web Store app install redirects to a blank page
The new URL is of the form:
https://admin.google.com/OauthTosCombined?appId=&redirectUri=https://apis.google.com/additnow/signin.html?applicationid%3D%26callback%3Dtrue%26parenturl%3Dhttps://chrome.google.com%26appfinder%3Dfalse
Has anyone been able to successfully enable this scenario? Thanks in advance!
One supported means of allowing an admin to install your Marketplace from a web site is the Integrate with Google button which may be worth considering ( https://developers.google.com/apps-marketplace/button?hl=ca ).
Does the install button from the Chrome Web Store standalone page not work correctly, or is it only when attempting to utilize the URL from the button on the page elsewhere? If the former is not working correctly, then it does sound like the linked to issue. Including the URL to the standalone Chrome Web Store page and an example of your app manifest would be helpful in identifying whether this is a bug.