I have a project including a problem.
After I enabled Datastore Admin, I clicked "Open Datastore Admin" button.
However, I faced an error of "500 Internal Server Error".
An error message is as follows.
The server has either erred or is incapable of performing the requested operation.
In other project, I can open Datastore Admin normally.
I deployed the program of correct project to GAE by eclipse, but same error has occurred.
I cannot find a solution, please help me.
There is a bug report for this issue:
https://code.google.com/p/googleappengine/issues/detail?id=10150&q=%22datastore%20admin%22&colspec=ID%20Type%20Component%20Status%20Stars%20Summary%20Language%20Priority%20Owner%20Log
"This looks to be a problem because you are using non-default authentication scheme.
Are you using user service/Google Accounts API for authentication of users inside your application? If not, consider changing your authentication method.
If you are, then you'll need to setup a custom domain and access the datastore admin via:
https://ah-builtin-python-bundle-dot-
so that the correct authentication cookies can be used."
I have the same issue, I'm using simpleauth for authentication and I suspect that is the problem... but I haven't solved it yet, changing my authentication scheme is not an option.
Related
I created a code in Bot-frame composer and published in azure Bot. We have used SSO(single sign-on) in the azure bot. Created a manifest file and published in app studio in MS teams. I am getting the messages twice when I open the chat for the first time. What is the solution to resolve it.
For this issue there are two different approaches to solve.
Check whether you are using webhooks or not. If you are using webhooks, check whether you are having multiple webhooks with same ID, which could send double messages.
This can be some weird approach. Sometimes, microsoft authentication issue will raise and if you are still having issue after checking webhooks, kindly contact the customer support of Microsoft and ask them to reset the app secret key and re-deploy the application.
There is another reason behind this, because of the previous login issues stored in SDK can cause the duplicate messages.
https://github.com/microsoft/botframework-sdk/issues/4387
https://github.com/microsoft/botframework-sdk/issues/5798
Check the above links for reference.
My team is in the process of developing an Office 365 add-in, specifically to enable interaction with a hosted web application, and we're encountering a "Permission needed / Bad Request" error that we can't seem to pin down.
Context:
Developing and testing the add-in involves configuring an Azure Active Directory v2 application via the management portal as well as (for development purposes) creating an xml manifest file (which is for v1 apps as opposed to the json format for v2) that can be side-loaded via the O365 interface to provide access to our hosted app (currently only xml manifests can be side-loaded). We're still very much in the process of figuring things out in Office 365, as well as Azure/Active Directory and Microsoft Graph, and the documentation is fairly broad and doesn't always seem to be up to date.
Problem Description:
One of the problems that we're run into occasionally is encountering a "Bad Request" dialog message (in a browser dialog titled 'Permission needed') that is displayed when clicking the toolbar icon for our add-in. The actual URL being requested is similar to https://store.office.com/client/consentnotification.aspx with a number of parameters representing our application and it's required permissions. This results in an HTTP 400 with "Bad Request" being the only response content.
This is happening when the user clicks on our add-in in the O365 application toolbar and is occurring at the point where the user would have to authorize permission for the add-in.
This error seems to be related to the application configuration, but we can't seem to sort out how specifically (ie, some developers are encountering it, and others are not. Sometimes it'll show up if we recreate the Azure Active Directory application using one version of portal or another (there are currently two, with the v2 version being in preview).
Can anyone offer suggestions as to what might be causing this or provide information on why this might be occurring? We're not blocked, but it is rather annoying to deal with in development. I've done a fair bit of research trying to sort out why this is happening and I've gone through a number of tutorials/introductions on configuring Azure apps without success.
This turned out to be related to the Azure Active Directory Application configuration.
For the applications where this was occuring, the AADv2 application manifest was using a "signInAudience" value of "AzureADMyOrg". For cases where it was working as expected (ie, properly populating the permission request dialog) the "signInAudience" was set to "AzureADandPersonalMicrosoftAccount".
After some testing, the solution for our particular problem seemed to be either manually editting the AADv2 application manifest (json) to have "signInAudience": "AzureADandPersonalMicrosoftAccount", or via the Portal by setting the Application's Authentication Supported Account Types setting to be "Accounts in any organizational directory" (this results in a manifest setting of "signInAudience": "AzureADMultipleOrgs" which also seems to work).
I have only ear file of the application and I need to deploy it on the server. I tried deploying it directly on my integrated weblogic server but because of security in the EAR, it is asking username/password from me and when I provide one from jazn file of the application, it does not accept.
Next I tried creating customization application of the ear and there I gave reference to jazn file while creating project. Now it is accepting my password but while running, it is throwing error -
[oracle.jbo.NoDefException][oracle.jbo.mom.DefinitionManager.findDefinitionObject][ApplicationCustomer]
I googled this error but seems like it is because it is not able to find business components from the corresponding model project. I added the model project as a dependency but still getting the same error.
Any ideas ?
You can create your own users directly in Weblogic, though Weblogic Console:
http://docs.oracle.com/cd/E21764_01/apirefs.1111/e13952/taskhelp/security/DefineUsers.html
Since users are server specific and not application specific, you can use these users to log on against your application.
For convenience reasons an ADF application can deploy users and roles, but thats only for testing purposes. In Production systems, users are not being deployed with the application, but either created through Weblogic Console or Enterprise Manager, or 'injected' by a Authentication Provider.
Another option would be to change passwords for the users deployed along with the application. On Weblogic Console, go to:
Security Realms -> My realm -> User and Groups -> select one of the users -> Passwords.
Then provide New Password and Confirm New Password fields. Save.
We currently have a Silverlight application which is hosted in a SharePoint 2010 page. The Silverlight app makes web service calls to a another server on our domain, which has a clientaccesspolicy file in place. We are experiencing cross-domain issues in our production environment.
Users in the farm admin group can use the Silverlight application without any issues. However, all other users recieve the generic cross domain exception when they try to use this app. We have attached Fiddler to the process and noticed that the farm admins are served the clientaccesspolicy file, but that non-admin users are not. In fact, Fiddler does not ever show an attempt to load this file for non-admins.
This only happens in our production environment, which leads me to believe there is a web config or permission setting causing the issue. Unfortunately, I cannot find anything that backs this up.
Has anyone else run into this issue or know if such a setting exists?
See comments above. I had to change the URL to use the full machine name i.e. from webserver/service.svc to webserver.domain.com/service.svc. It solved the problem but doesn't answer the question about why the farm admins could access it. vorrtex's response is the best possible explanation I have seen so far.
When I try to access the Datastore Admin page in my GAE app, i get the following error
Error: Server Error
The server encountered an error and could not complete your request.
If the problem persists, please report your problem and mention this error message and the query that caused it.
I have switched it on in my app.yaml
builtins:
- datastore_admin: on
I am not even able to download data from the datastore. I get the error Authentication failed.
What could be the reason ?
The bug is something to do with using custom domain. When I create a normal application and upload the code, it works fine. Only when I have a custom domain, i get the problem
I changed the apps's authentication method from Google Apps Domain to Google Accounts API and it now works.
look at the procedure in this documentation.
Maybe you forgot to add :
builtins:
- remote_api: on
Hope it help!