While trying to access the Experience manager, I was getting following error.
There was a problem with your request: faultCode:Server.Error.Request faultString:'HTTP request error' faultDetail:'Error: [IOErrorEvent type="ioError" bubbles=false cancelable=false eventPhase=2 text="Error #2032"]. URL: http://10.11.33.111:8000/ifcr/wb//landing/LandingPagesGroups.action'
See the screenshot as well.
Maybe the error 2032 on endeca workbench happens if you open workbenches in two browser windows at the same time, and logout from one window and then try to login again while the workbench is open in another window. Close Workbench in other browsers and then logout and login.
This happens due to open Endeca experience manager in multiple tabs. Delete cookies and try.
However, you can use different browser to open experience manager using same id and password
Related
After installation of openfire version 4.6 I was able to access console in browse http://domain:9090
and database also imported in mysql but when come to profile set up I am facing this error:
url: http://domain:9090/setup/setup-profile-settings.jsp
A failure occurred while fetching your session from the server. This is typically a cookie issue. Please either clear all cookies for this domain or try this URL again from an incognito browser session.
That was nothing but restart openfire and follow again. There will be no error.
I am trying to connect PowerBI with Highrise CRM using CData's (the company's), ODBC Connector but every time I try to test the connection, it gives a '401 unauthorized' error. I have admin rights in both, the system and Highrise, the credentials are correct as well. It does not open a browser window asking for access, as it should once it's successfully connected.
I created the app as required and put in the Redirect URI as http://localhost:2435, both in the app as well as the connector. I tried resetting the connection, tried removing the connector and adding it again but nothing seems to work. I get the same error every time. I have also triple checked the OAuth 2.0 credentials from the app and they are correct as well.
I am not able to figure out where exactly the problem lies. I have the log file for it but I am not sure what part of it would be beneficial to post here to troubleshoot.
Trying to execute this command in Visual Studio Package Manager Console:
Scaffold-DbContext "Server=my_server\SQLEXPRESS;Database=FoodStore;Trusted_Connection=True;" Microsoft.EntityFrameworkCore.SqlServer -OutputDir Models
but I'm getting this error:
Cannot open database "FoodStore" requested by the login. The login
failed. Login failed for user 'MicrosoftAccount\my_email#gmail.com'.
I've tried creating a login in Security for 'MicrosoftAccount\my_email#gmail.com' as db_owner in Microsoft SQL Management Service Studio, as well as signing in with local accounts instead, but I'm still getting an error in Visual Studio when running Scaffold-DbContext.
I was also facing the same error but Ifound the solution. In scaffolding string I am using the server name "LAPTOP-82GAEQ6T\SQLEXPRESS" but in SQL server I am using only "LAPTOP-82GAEQ6T". That's the same error I was facing, please check your server connection name on both sides, on the server side and your connection string. Best of luck.
I encountered the same issue as you have mentioned i.e.
Cannot open database "dbxxxxx" requested by the login. The login failed.
Login failed for user 'xxxxx\xxx'.
And after working around with it, I found that I had to carefully check the value of
server attribute.
"Server=.\SQLEXPRESS;Database=FoodStore;Trusted_Connection=True;" also works well.
I wrote an app and I am trying upload it on Azure. The app runs ok locally and has a SQL Server database as the backend; the app is based off MVC.
When I try to access a page such as /person, I get this error:
Azure Exception Details: System.Data.SqlClient.SqlException: Login failed for user 'null'.
Anyone ever dealt with such an error and how did you resolve it.
I have tried a few suggestions but none seems to work:
adding to config file
setting Persist Security Info=False to true
What is the best way to solve this?
On the app's data connection, the connection string had no userid. Adding a userid fixed the issue. Even though when the app was published with a proper connection string, the user id was empty.
Environment:
MFP 6.3 Studio Windows 7
MFP 6.3 Server (WAS LC)
Downloaded the form-based sample from the IBM MobileFirst Platform Developer Center.
In MFP 6.3 Studio, the sample runs fine.
I then change my build settings and Build All Environment -> get the new wlapp file.
I get my war file from the MFP 6.3 Server. Open up and put in the modified authenticationConfig.xml
Basically it's just transferring the one snippet from the studio authenticationConfig.xml to the xml file within the WAR file.
<customSecurityTest name="DummyAdapter-securityTest">
<test isInternalUserID="true" realm="SampleAppRealm"/>
</customSecurityTest>
I restart the server and deploy the .wlapp and .adapter files.
In the standalone server, I run the preview mode. I Enter the username and password and login. It didn't login and I see these errors on the server console.log.
[ERROR ] SESN0008E: A user authenticated as anonymous has attempted to access a session owned by user:BasicRegistry/demo.
[ERROR ] SRVE0232E: Internal Server Error. Exception Message: [com.ibm.ws.webcontainer.webapp.WebAppErrorReport: com.ibm.websphere.servlet.session.UnauthorizedSessionRequestException: SESN0008E: A user authenticated as anonymous has attempted to access a session owned by user:BasicRegistry/demo.
at com.ibm.ws.webcontainer.session.impl.HttpSessionContextImpl.checkSecurity(HttpSessionContextImpl.java:686)
at [internal classes]
at com.worklight.core.auth.impl.AuthenticationFilter.associateAuthContextWithThread(AuthenticationFilter.java:426)
at com.worklight.core.auth.impl.AuthenticationFilter.doFilter(AuthenticationFilter.java:145)
at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:194)
at [internal classes]
Caused by: com.ibm.websphere.servlet.session.UnauthorizedSessionRequestException: SESN0008E: A user authenticated as anonymous has attempted to access a session owned by user:BasicRegistry/demo.
... 7 more
]
[ERROR ] SRVE0777E: Exception thrown by application class 'com.worklight.core.auth.impl.AuthenticationContext.checkAuthentication:604'
com.worklight.server.auth.api.WorkLightAuthenticationException
at com.worklight.core.auth.impl.AuthenticationContext.checkAuthentication(AuthenticationContext.java:604)
at com.worklight.core.auth.impl.AuthenticationContext.processRealms(AuthenticationContext.java:469)
at com.worklight.core.auth.impl.AuthenticationContext.pushCurrentResource(AuthenticationContext.java:443)
at com.worklight.core.auth.impl.AuthenticationServiceBean.accessResource(AuthenticationServiceBean.java:75)
at com.worklight.integration.services.impl.DataAccessServiceImpl.invokeProcedureInternal(DataAccessServiceImpl.java:430)
at com.worklight.integration.services.impl.DataAccessServiceImpl.invokeProcedure(DataAccessServiceImpl.java:139)
at com.worklight.gadgets.serving.handler.BackendQueryHandler.getContent(BackendQueryHandler.java:95)
at com.worklight.gadgets.serving.handler.BackendQueryHandler.doPost(BackendQueryHandler.java:56)
at com.worklight.gadgets.serving.GadgetAPIServlet.doGetOrPost(GadgetAPIServlet.java:148)
at com.worklight.gadgets.serving.GadgetAPIServlet.doPost(GadgetAPIServlet.java:108)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:595)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1240)
at [internal classes]
at com.worklight.core.auth.impl.AuthenticationFilter$1.execute(AuthenticationFilter.java:217)
at com.worklight.core.auth.impl.AuthenticationServiceBean.accessResource(AuthenticationServiceBean.java:76)
at com.worklight.core.auth.impl.AuthenticationFilter.doFilter(AuthenticationFilter.java:222)
at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:194)
at [internal classes]
After studying the securityIntegrationEnabled="false workaround, I think I have figured out why things are working / not working.
The solution is actually very simple without changing the server.xml.
When the error SESN0008E occured, I was testing the FormAuth app using the common preview mode by clicking on the link from the admin console in the standalone server. Although the common preview link opened to a new browser, but the sessionID actually stays. Both browser tabs are in the same session (I checked).
It means that the sessionID that I am using is actually the one that was already authenticated by the Admin Console. And in my preview mode I tried to authenticate again in the session that was already "owned" by another user. This causes WAS to throw the error SESN0008E: A user authenticated as anonymous has attempted to access a session owned by user:BasicRegistry/demo. My app preview is in the same httpsession as the admin console, and hence the error.
So to get it to work, I copy the preview link. Close all the browser to ensure the sessions are killed. Open a new browser, paste the preview link and the FormAuthentication works now.
A maybe more convenient solution would be to create a mobile web environment and use that for preview testing.
In WAS and WAS Liberty profile, security integration is enabled by default. This also means that:
... session management facility associates the identity of users with
their HTTP sessions. This feature will mark a session as "owned" by
the first user that accesses a session that is not already marked as
owned.
If a session is already marked as owned, it will check that
the owner is the same as the current user. If not, rather than
granting access to the session, at minimum a message with identifier
SESN0008E will be logged and access to the session will not be
granted.
In some cases, an UnauthorizedSessionRequestException is
thrown, with message SESN0008E as the cause.
In the MobileFirst Development Server in Eclipse, the underlying WAS Liberty's server.xml has this disabled.
For your POC as a workaround, you can disable the feature by adding in the server.xml file the following entry: <httpSession securityIntegrationEnabled="false"/>
Note that adding this setting is global to all applications and can impact negatively on existing applications on the server, if in existance.