I get this error:
"An error occurred (InvalidToken) when calling the PutObject operation: The provided token is malformed or otherwise invalid."
When I create object from django rest admin panel in vercel server and when I create it in local it works. How to integrate aws s3 + vercel to django?
Failed to find a valid digest in the 'integrity' attribute for resource 'http://localhost:90/_framework/Heir.Blazor.Manager.dll' with computed SHA-256 integrity 'f3IxbqueH8AxtH+5Q92IoxZgKnnKFzO2hJc0KDJWovE='. The resource has been blocked.
login:1 Unknown error occurred while trying to verify integrity.
blazor.webassembly.js:1 Error: Failed to start platform. Reason: TypeError: Failed to fetch
at At (blazor.webassembly.js:1:59510)
I have been given with the credentials and endpoint from Radixx but when I used to use the endpoint to get security token . I am getting this error :
Additional Source Information: ERR9999: Unexpected error in GetSecurityGUID.Error Generation Source Location: DSAIXUAT1APP01 Session ID: -1 Error Details: Your user ID and Password combination did not validate.
Can anyone tell me why WSo2 API Manager does not authenticate? I have set up two WSo2 API Manager 1.8.0 instances and created an api.it is working fine as prototyped api. after it save and publish and call the api with an access token
getting the following rsponce
<ams:fault xmlns:ams="http://wso2.org/apimanager/security">
<ams:code>900906</ams:code>
<ams:message>
No matching resource found in the API for the given request
</ams:message>
<ams:description>
Access failure for API: /api/stature, version: 1.0.0 with key: null
</ams:description>
</ams:fault>
and here is the wso2carbon.log:
TID[-1234] [AM] [2015-01-19 00:12:47,263] ERROR {org.wso2.carbon.apimgt.gateway.handlers.security.APIAuthenticationHandler} -
API authentication failure org.wso2.carbon.apimgt.gateway.handlers.security.oauth.OAuthAuthenticator.authenticate(OAuthAuthenticator.java:212)
org.wso2.carbon.apimgt.gateway.handlers.security.APIAuthenticationHandler.handleRequest(APIAuthenticationHandler.java:94)
org.apache.synapse.rest.API.process(API.java:284) org.apache.synapse.rest.RESTRequestHandler.dispatchToAPI(RESTRequestHandler.java:83)
org.apache.synapse.rest.RESTRequestHandler.process(RESTRequestHandler.java:64)
org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:220)
org.apache.synapse.core.axis2.SynapseMessageReceiver.receive(SynapseMessageReceiver.java:83)
org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
org.apache.synapse.transport.passthru.ServerWorker.processNonEntityEnclosingRESTHandler(ServerWorker.java:344)
org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:168)
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
java.lang.Thread.run(Thread.java:745)
No matching resource found in the API for the given request
The above issue occurs, when your request URL is wrong and APIManager could not match that with existing published APIs.
If the published API configuration is not deployed properly in the gateway. You can check this, browsing to Gateway's synapse config folder/api folder.(inside/repository/deployment/server)
If the relevant API entries are missing at APIM DB.
Do you try with distributed setup? did you change DBs? Check above all 3 points, then you can figure out the issue quickly.
I have a Worklight app and I am trying to set up an adapter to capture client-side logs from it. (I have first tried to use Analytics, but it keeps crashing with PermGen out of memory error, perhaps I will have to look at it if this fails.) I followed the steps described in http://www-01.ibm.com/support/knowledgecenter/#!/SSZH4A_6.2.0/com.ibm.worklight.dev.doc/devref/c_uploaded_client_log_data.html up to "Server security". I have no idea how to actually configure the server realm/security check/etc. for the log uploader servlet. Currently it returns this error (both on development and production server):
[ERROR ] FWLSE0059E: Login into realm 'WLRemoteDisableNullLoginModule' failed. Cannot find application 'null'. [project Project]
Cannot find application 'null'
[ERROR ] FWLSE0117E: Error code: 4, error description: AUTHENTICATION_ERROR, error message: An error occurred while performing authentication using loginModule WLRemoteDisableNullLoginModule, User Identity {wl_directUpdateRealm=null, wl_authenticityRealm=null, Project=(name:2, loginModule:ProjectLoginModule), wl_remoteDisableRealm=null, SampleAppRealm=null, wl_antiXSRFRealm=null, wl_deviceAutoProvisioningRealm=null, WorklightConsole=null, wl_deviceNoProvisioningRealm=null, myserver=(name:2, loginModule:ProjectLoginModule), wl_anonymousUserRealm=null}. [project Project] [project Project]
[ERROR ] FWLSE0059E: Login into realm 'WLRemoteDisableNullLoginModule' failed. Cannot find application 'null'. [project Project]
Cannot find application 'null'
[ERROR ] FWLSE0117E: Error code: 4, error description: AUTHENTICATION_ERROR, error message: An error occurred while performing authentication using loginModule WLRemoteDisableNullLoginModule, User Identity {wl_directUpdateRealm=null, wl_authenticityRealm=null, Project=(name:2, loginModule:ProjectLoginModule), wl_remoteDisableRealm=null, SampleAppRealm=null, wl_antiXSRFRealm=null, wl_deviceAutoProvisioningRealm=null, WorklightConsole=null, wl_deviceNoProvisioningRealm=null, myserver=(name:2, loginModule:ProjectLoginModule), wl_anonymousUserRealm=null}. [project Project] [project Project]
[ERROR ] com.worklight.core.messages:Invoke procedure failed due to: null
[ERROR ] com.worklight.core.messages:Invoke procedure failed due to: null
I tried uncommenting the customTests section in authenticationConfig.xml containing the wl_remoteDisableRealm, but to no avail.
How should this be configured?
I see from your comment you got it working. We did not want to duplicate documentation for authenticationConfig.xml and risk it getting out of sync on the "Server preparation for uploaded log data" KnowledgeCenter topic page in the "Server security" section. That said, we should have provided a link to the Worklight Security Framework topic page.
There is nothing special or unique about the configuration for log receiver servlet in the context of security. The point being made in that section is that if you configure authenticationConfig.xml so that security issues challenges to the app that requires user interaction, you should
send logs only when you are sure your are already authenticated, or
change security constraints such that the log upload servlet URL authentication does not require user interaction
If you leave these in place, the risk is that the end-user will see a random prompt for credentials when they do not expect it.
The reason the "Server preparation for uploaded log data"