Enterprise authentication Mode Login error

Hi Gurus,
I am having issues logging into webi client station with Enterprise authentication mode couldn't login, I trying to run it on administrator account.
I was able to login through Standalone mode but not with other types of modes.
As I am working on Universes with secured connection type it has to be on Enterprise mode in webi. Please correct me if my assumption is wrong.
Thanks in Advance.
Speedsin

Hi,
Check in CMC whether your login user (administrator) has all the required accesses or not.
Cheers,
Suresh

Similar Messages

Error when creating connection with SSO Authentication mode

Hi All,
when I am creating the connection with Authentication Mode as SSO, I get error "Unable to connect to SAP BW Server User abc has no RFC Authorization for function group SYST".
When I am craeting connection with specific user id and Password it works fine.
Pls. let me know whats the problem with creating connection with SSO.
System Info: BOXIR.3.1 Sp3, SAP 7.1
Regards,
Nisha

Yes, I have installed Integration Kit, and configured the SSO.
I am able to login into designer with Authentication as SAP.
But, the Problem is with connection creation with SSo authentication mode.
Is there any property or role needs to be defined for the universe designer Group or user, so that SSO is allowed in authentication mode?
Regards,
Nisha

Oracle Enterprise Manager 11g - 'unexpected login error'

Hi,
I am having trouble logging into Oracle Enterprise Manager - Fusion Middleware Control. at the login screen when i enter in the UN and PWD, I get the msg: 'unexpected login error'. I was able to login before, this just happend and now I cannot login. Any help would be appreciated.
Thanks.

You may have greater chances to get an answer....there:
Enterprise Manager
Greetings...
Sim

Get an error for changing the windows authentication mode to the both SQL and windows authentication mode

I installed the SQL server Express 2008 R2 and then SQL Server Management Studio 2008 R2 . But during the installation, I could not choose the both SQL and windows authentication mode and an error accrued so I did that just with windows authentication mode.
Now, I want to change the windows authentication mode account to the SQL authentication mode but it shows me an error which is you do not have permission (Although I am the administrator in windows), what can I do?
Following steps are the steps that I went but I got an error:
Server properties >> security >> choose the option of SQL Server and Windows Authentication mode
and the error that I got is attached(access is denied)
Can you please help me?

You can change the setting after you gain admin rights to your SQL Server. You don't admin rights automatically, you have to explicitly add yourself during the install
Here's a guide on how to (re)gain those rights:
http://v-consult.be/2011/05/26/recover-sa-password-microsoft-sql-server-2008-r2/

SP 2013 Upgrade error - web application is configured with claims authentication mode however the content database you are trying to attach is intended to be used against a windows classic authentication mode.

Hi there,
I get this error when I perform a DB Attach upgrade from SharePoint 2010 to SharePoint 2013.
"web application is configured with claims authentication mode however the content database you are trying to attach is intended to be used against a windows classic authentication mode."
Any help is appreciated. Thanks.

There is other way of fixing this issue apart from what Amit mentioned. Create a classic based web application in SP 2013 using PowerShell.
New-SPWebApplication -Name "TestApplication" -ApplicationPool "TestApplicationAppPool" -AuthenticationMethod "NTLM" -ApplicationPoolAccount (Get-SPManagedAccount "sppoc\spfarm") -Port 100 -URL "http://sp2013demo"
Now mount the content database from SP 2010 on to the web application created above
Mount-SPContentDatabase WSS_Content_100 -DatabaseServer SQL2012Demo -WebApplication http://sp2013demo:100
Once the mount is complete, convert the web application to use claims and migrate the user to use claims identity.
Convert-SPWebApplication -Identity "http://sp2013demo:100" -To Claims –RetainPermissions -Force
$w = Get-SPWebApplication "http://sp2013demo:100"
$w.MigrateUsers($True)
See my blog post about it: http://www.sharepointnadeem.com/2014/01/upgrade-from-sharepoint-2010-classic.html
Please remember to up-vote or mark the reply as answer if you find it helpful.

Login error in 3-tier mode Deski

Hi,
We are getting below error when we try to open 3-tier deski from infoview:
"[repo_proxy 13] HttpSessionFacade::openSession - unable to proceed to the handshake : HTTP communication problem".
Below is detail description of issue how it happened:
1. Users were unable to login to CMC, but they were able to login to Infoview.
2. We found that tomcat process was hung. Therefore we restarted the tomcat.
3. After this first error was resolved. But 3-tier login error started.
We did following thing to resolve the issue:
1. We found that there are no patched applied on server recently.
2. Veryfied and found that All require ports like 6400, 8080 are opened.
3. Users are able to telnet to server from there local machine.
4. We deleted all the entries in the LocData Folder on the client.
5. Tried to restart Tomcat and all the BO Services again.
6. Did the port binding for the CMS and the Deski Services.[Input the IP address/hostname in the place of the Auto Align in the
    CMS server properties]
But it did not help. Issue is still there. We also fould below error in catalina.out when we restarted tomcat:
"Port number is already in use: 8000u201D.
Below are my environment details:
===============================================================================
Product: BOXI R3.1 FP1.8
CMS DB: Oracle 10g
OS:Linux
Tomcat - Apache: 5.2
===============================================================================
Please help me in this. Any help would be greatly appreciated.
Thanks,
Swapnil Rodge.

Hi,
We are getting below error when we try to open 3-tier deski from infoview:
"[repo_proxy 13] HttpSessionFacade::openSession - unable to proceed to the handshake : HTTP communication problem".
Below is detail description of issue how it happened:
1. Users were unable to login to CMC, but they were able to login to Infoview.
2. We found that tomcat process was hung. Therefore we restarted the tomcat.
3. After this first error was resolved. But 3-tier login error started.
We did following thing to resolve the issue:
1. We found that there are no patched applied on server recently.
2. Veryfied and found that All require ports like 6400, 8080 are opened.
3. Users are able to telnet to server from there local machine.
4. We deleted all the entries in the LocData Folder on the client.
5. Tried to restart Tomcat and all the BO Services again.
6. Did the port binding for the CMS and the Deski Services.[Input the IP address/hostname in the place of the Auto Align in the
    CMS server properties]
But it did not help. Issue is still there. We also fould below error in catalina.out when we restarted tomcat:
"Port number is already in use: 8000u201D.
Below are my environment details:
===============================================================================
Product: BOXI R3.1 FP1.8
CMS DB: Oracle 10g
OS:Linux
Tomcat - Apache: 5.2
===============================================================================
Please help me in this. Any help would be greatly appreciated.
Thanks,
Swapnil Rodge.

Issue with the Authentication mode:

Hello Guru's
I have installed P6 Primavera and when I am trying to login to
http://localhost:8080/primaveraweb/action/login
It is giving the below error -
"Primavera P6 was configured to use a different authentication mode that the database selected"
I checked the authentication mode in the P6 Administrator scrren where it shows that the
Authentication
Mode: NATIVE
Web Single Sign-On
User Name Header Key: OAM_REMOTE_USER
Context Path Override: /primaveraweb
Server and Port override: http://<hostname>:8080 ----- I can see the correct hostname address.
Gurus, please help me on this ASAP.
Thanks
Venu

Hello Guru's,
I could able to resolve the error by following the Admin Guide.
This error is because you have migrated the PSUP database which is having the LDAP authentication mode, but the P6 Primavera is in NATIVE authentication mode.
NOTE: A configuration for P6 Web Access might include database instances that are not set to the same authentication mode as the server of P6 Web Access.
If a user connects and requests a database that is set to a different authentication mode than the server of P6 Web Access, an error message displays.
The user must select a database that matches the authentication mode set for the server of P6 Web Access.
I resolved the issue using the below steps:
Run the D:\Oracle\installers\Enterprise Project Portfolio Management\P6_70_Client_Applications\install\database\ldap-config\ LDAPCfgWiz.exe
Login as privuser for PMDB and select the authentication mode as “NATIVE”
Login as privuser1 for MMDB and select the authentication mode as “NATIVE”
Bounce the P6 Admin Server.
Thanks
Venu

InfoPath 2010 does not work in claims authentication mode on SharePoint 2010

Hi everyone,
I created an Infopath 2010 Forms published on a Claims-based authentication site collection. This form has an external datasource plugged on the
_vti_bin/UserProfileService.asmx webservice (within the same site collection). This datasource is queried when the form opens. When I check this form with Infopath designer preview, everything works fine.
But once this forms is published, an error "Error while trying to contact Web Service" occured when opening a new form.
Here ere an extract of the logs:
The following query failed: GetUserProfileByName (User: DOMAIN\username, Form Name: library, IP: , Connection Target: , Request: http://server/_layouts/FormServer.aspx?xsnLocation=http://server/library/forms/template.xsn?DefaultItemOpen=1&Source=http://server/page.aspx, Form ID: urn:schemas-microsoft-com:office:infopath:library:-myXSD-2010-01-12T23-08-28 Type: DataAdapterException, Exception Message: The remote server returned an error: (500) Internal Server Error.
Server was unable to process request. ---> Attempted to perform an unauthorized operation.
The remote server returned an error: (500) Internal Server Error.)
Here is an extract of my IIS log:
2010-11-25 13:45:30 fe80::b9ab:23d9:ff9e:bb23%11 POST /_vti_bin/userprofileservice.asmx - 50000 - fe80::b9ab:23d9:ff9e:bb23%11 InfoPathDA 500 0 0 41
Additionnaly, you have to know :
If we set the web application authentication mode in "Classic mode", everything work fine
As soon as we set "Claim mode authentication", we reproduce the issue and this even if we are using a Windows integrated  account or an external account (SQL Memberships, Claims/AD)
We reproduce this issue in different SharePoint FARM.
It seems that this issue is generic with "Claims mode authentication" and i'm not shure that other forum can help us.
How can I make this WebService works for my form?
Thanks in advance.
Seb Nicot

I am not sure but a Code Solution might work ... I assume InfoPath 2010 is not Claims-Based aware.
I am on SP1 and June 2011 CU but still had no luck
If you only need the current user’s login name, then in the “FormEvents_Loading” event, you can retrieve the current user name with a call to the “Application.User.LoginName” property. Here is an example:
        public void FormEvents_Loading(object sender, LoadingEventArgs e)
            XPathNavigator codeUserNameXPN = this.CreateNavigator().SelectSingleNode(
                "/my:myFields/my:CodeRetrievedUserName", this.NamespaceManager);
            codeUserNameXPN.SetValue(this.Application.User.LoginName);
OR ----------------
        public void FormEvents_Loading(object sender, LoadingEventArgs e)
            //A place to write the results
            XPathNavigator codeUserNameXPN = this.CreateNavigator().SelectSingleNode(
                "/my:myFields/my:CodeRetrievedUserName", this.NamespaceManager);
            //codeUserNameXPN.SetValue(this.Application.User.LoginName);
            try
                //ThresholdAuthentication is the web service reference to the
                //https://test:24575/_vti_bin/authentication.asmx web service
                GetUserName.ThresholdAuthentication.Authentication authenticationWS =
                    new GetUserName.ThresholdAuthentication.Authentication();
                //Call the web service's Login method and pass the username and password of a site
                //administrator so we have rights to read all user profiles
                authenticationWS.Url = "https://test:24575/_vti_bin/authentication.asmx";
                authenticationWS.CookieContainer = new System.Net.CookieContainer();
                GetUserName.ThresholdAuthentication.LoginResult result = authenticationWS.Login(
                    "Admin", "Pa$$w0rd");
                if (result.ErrorCode == GetUserName.ThresholdAuthentication.LoginErrorCode.NoError)
                    //If we authenticated correctly, then set up a call to the user profile service
                    //ThresholdUserProfileService is the web service reference to the
                    //https://test:24575/_vti_bin/userprofileservice.asmx web service
                    GetUserName.ThresholdUserProfileService.UserProfileService userProfileWS =
                        new GetUserName.ThresholdUserProfileService.UserProfileService();
                    //Pass the authentication cookies we got back from the authentication web service
                    userProfileWS.Url = "https://test:24575/_vti_bin/userprofileservice.asmx";
                    userProfileWS.CookieContainer = authenticationWS.CookieContainer;
                    //Try to find the user profile information of the current
                    GetUserName.ThresholdUserProfileService.PropertyData[] resultData =
                        userProfileWS.GetUserProfileByName(this.Application.User.LoginName);
                    //Enumerate through the properties
                    foreach (GetUserName.ThresholdUserProfileService.PropertyData property in resultData)
                        //Pick out the "AccountName" property and display it
                        if (property.Name == "AccountName")
                            codeUserNameXPN.SetValue(property.Values[0].Value.ToString());
                else
                    //If we failed to authenticate properly, display the reason why
                    codeUserNameXPN.SetValue(result.ErrorCode.ToString());
            catch (System.Exception ex)
                //If an exception occurred, report it.
                codeUserNameXPN.SetValue(ex.Message);
Note that in order for this code to work, you will need to make your form template fully-trusted in the “Security” section of the “Form Options” dialog, and then publish your form template to SharePoint as an Administrator-Approved form
template

There is an inconsistency between the authentication mode of target web application and the source web application after migrating to claims

I've had my farm upgraded from SP2010 to SP2013 for over 6 months now and all is well, however, I was refreshing my staging environment from production and I noticed that one of the databases still shows these errors when I run test-spcontentdatabase:
Category : Configuration
Error : False
UpgradeBlocking : False
Message : The [SharePoint Web App] web application is configured with claims authentication mode however the content database you are trying to attach is intended to be used against
a windows classic authentication mode.
Remedy : There is an inconsistency between the authentication mode of target web application and the source web application. Ensure that the authentication mode setting in upgraded web application is the
same as what you had in previous SharePoint 2010 web application. Refer to the link "http://go.microsoft.com/fwlink/?LinkId=236865" for more information.
This doesn't make sense considering I converted the production web application to claims during the upgrade and then verified all sites were working with claims logins. I also verified that existing AD user identities were converted to claims by checking out
the database tables. Yet test-spcontentdatabase still thinks there is a mismatch here.
My farm is SP1 and no further CUs. The point of this particular refresh is so I can update to the November CUs in my test farm. Anyone else see this? Seems like it's a bug/safe to ignore because my stuff is working.
Thanks,
Aaron

See:
http://thesharepointfarm.com/2014/11/test-spcontentdatabase-classic-to-claims-conversion/
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Xdb and authentication-mode

hi,
i use xdb's httpserver as gateway to plsql, instead of apache's mod_plsql.
i set a DAD and configured it with basic authentication. everything works fine.
but basic authentication uses db users, however i need to use application users to authenticate. that is why i tried to use globalowa authentication-mode.
i also implemented "authorize" function for globalowa
problem starts just here.
first of all, dbms_epg doesnt support for "password" attribute in DAD, which is a "should be" for any custom authentication.
when i skip this attribute and try to access a url, it prompts basic login screen, however, there is no way to get in. even i use xdb' uname/pwd, i get a 404 error.
i am not sure if custom authentication is supported in xdb's httpserver. if any of you had tried xdb as gateway, any advice would be helpful.
if this feature is not supported , what are my options?
thanks in advance

lavagirl05 wrote:
AirPort Admin Utility
download *airport utility* (http://support.apple.com/downloads/AirPortUtility_5_41) and launch it. now double-click on your express to enter +manual setup+. in the next window, you should see what you're looking for.
JGG

Login error with BOXI 3.1

I frequently get a login error with BO XI 3.1 (with fix patched 1.3 and SAP interface installed on Linux machine).
ERROR:
Account information not recognized: The property SI_GUID of info object with id number 1876 is not unique. Table = 'CMS_InfoObjects6'. Column = 'SI_GUID'.
(authentication type: enterprise)
Error comes after first logging out with User1 and then trying to login again immediately with User2 (with IE6).
Thanks, Timo

Hello again,
Just to answer your questions:
- Yes, all systems are in the same domain
- I have configured BOE for SAP SSO. Users and roles have been imported.
- The SAP Portal is sending the ticket.
We've been able to reproduce the error over different client machines, and a workaround involves closing the browser window (with the error) that gets launched from SAP Portal on the first attempt and then clicking through to BO from the SAP Portal again. It works fine after that, but I'm afraid that some users might find this annoying/alarming
Thanks,
Myla

Login Error in BI launch Pad as user, BOBJ 4.0

Hi Expert,
I am not able login as user in Business object launch pad in order to check the folder assignment to user, error as follow upon login,
"Account Information Not Recognized: Enterprise authentication could not log you on. Please make sure your logon information is correct. (FWB 00008)"
Imported the Role from BI to business object environment after assigned to test user and performed the folder assignment to group in CMC, i am using BI logon Authentication for BI test user.
Note: As a Admin i am only able to logon with the Authentication as Enterprise, not as SAP not sure if that has any thing do for the error.
I am new to Business object 4.0 security, your help to resolve the issue will be greatly appreciated.
Best Regards,
Asher

Hi Asher,
To get you right:
- you have imported the roles from your BW system
- you have imported the BW users within this role into BO
right?!
What is important is that you understand that there is different type of users. The one you imported from your BW system is a SAP user so this is normal that you have to use SAP and not Enterprise as authentication medthod. Administrator is an Enterprise user so SAP will not work.
SAP User are formatted like this when you import them (can be changed):
<SID>~<CLIENT>/<USER_NAME>
Then you have a concept of ALIAS, it means that your SAP User could have a enterprise or a AD alias for example and this enables you to use additional authentication method.
However I think for your test user, you should use the SAP authentication and the error you are getting is just by-design.
Cheers.

Data Federator authentication modes

In Data Federator (3.0 SP1 or previous), Is there any authentication mode similar to AD/LDAP in BOE?
What are the options available for dynamic logon, while connecting to a database via JDBC in the DF Data source definition screen?
Thanks
Tiji

Hi Tiji,
Connecting to Data Federator using BOE applications
In Data Federator XI 3.0 SP1 and previous versions the only way to connect to Data Federator is to provide a user name and password. Data Federator manages its own repository of users.
Using Universe Designer, you can create a Data Federator connection with two authentication modes:
- Configured Identity: the same user name and password is used for all consumers of the connection
- Database Mapping: the DBUser and DBPassword associated to the BOE user are used to connect to Data Federator.
There is no support for single sign on.
Creating a datasource using Data Federator Designer*
When you register a new datasource using Data Federator Designer you have three authentication modes supported:
- Configured Identity: the same user name and password is used to connect to the database (for all DF users).
- Principal Mapping: a mapping can be defined between a DF user and data source credentials. This is done through creating and managing "login domains".
- Caller Impersonation: the DF user and DF password is used to connect to the data source.
The Principal Mapping mode is pretty similar to the feature in BOE called Database Mapping except that you are not restricted to a single DBUser/DFPassword pair whatever data source you want to access. This is more flexible. Note that there is no UI in Administrator to manage login domains. You have to run built in stored procedures in the query tool.
Hope this helps,
Mokrane
Mokrane Amzal
Software Development Manager
SAP BusinessObjects Divison

Invalid Login error while trying to login to OIM console

Hi,
I have installed OIM 11gR2 in my local environment. It was working fine a day back but post installation of OAM, I am unable to login to OIM console with the correct credentials. OIM and OAM had been installed in the same domain. I deleted the OAM server but even after that it is not working. Getting the following error :
<Oct 23, 2013 11:27:25 AM IST> <Error> <Default> <BEA-000000> <Failed to communicate with any of configured Access Server, ensure that it is up and running.>
java.lang.reflect.InvocationTargetException
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:606)
        at oracle.idm.common.login.SignInBean.handleWeblogicAuthn(SignInBean.java:127)
        at oracle.idm.common.login.SignInBean.doLogin(SignInBean.java:97)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:606)
        at com.sun.el.parser.AstValue.invoke(AstValue.java:187)
        at com.sun.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:297)
        at org.apache.myfaces.trinidadinternal.taglib.util.MethodExpressionMethodBinding.invoke(MethodExpressionMethodBinding.java:53)
        at org.apache.myfaces.trinidad.component.UIXComponentBase.broadcastToMethodBinding(UIXComponentBase.java:1415)
        at org.apache.myfaces.trinidad.component.UIXCommand.broadcast(UIXCommand.java:183)
        at oracle.adf.view.rich.component.fragment.UIXInclude.broadcast(UIXInclude.java:103)
        at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent$1.run(ContextSwitchingComponent.java:92)
        at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent._processPhase(ContextSwitchingComponent.java:361)
        at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent.broadcast(ContextSwitchingComponent.java:96)
        at oracle.adf.view.rich.component.fragment.UIXInclude.broadcast(UIXInclude.java:97)
        at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:475)
        at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:756)
        at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._invokeApplication(LifecycleImpl.java:957)
        at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:427)
        at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:207)
        at javax.faces.webapp.FacesServlet.service(FacesServlet.java:265)
        at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
        at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
        at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301)
        at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
        at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
        at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:205)
        at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
        at oracle.adf.view.page.editor.webapp.WebCenterComposerFilter.doFilter(WebCenterComposerFilter.java:117)
        at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
        at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:128)
        at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:446)
        at oracle.adfinternal.view.faces.activedata.AdsFilter.doFilter(AdsFilter.java:60)
        at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:446)
        at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:271)
        at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:177)
        at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)
        at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
        at oracle.help.web.rich.OHWFilter.doFilter(Unknown Source)
        at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
        at oracle.iam.ui.platform.servletfilter.IdentityContextFilter.doFilter(IdentityContextFilter.java:50)
        at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
        at oracle.adf.library.webapp.LibraryFilter.doFilter(LibraryFilter.java:180)
        at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
        at oracle.iam.ui.platform.view.authz.filter.AdvancedConsoleAccessFilter.doFilter(AdvancedConsoleAccessFilter.java:125)
        at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
        at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
        at java.security.AccessController.doPrivileged(Native Method)
        at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:324)
        at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:460)
        at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
        at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
        at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
        at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
        at oracle.security.am.agent.wls.filters.OAMServletAuthenticationFilter.doFilter(OAMServletAuthenticationFilter.java:264)
        at oracle.security.am.agent.wls.filters.OAMValidationSystemFilter.doFilter(OAMValidationSystemFilter.java:133)
        at oracle.security.wls.oamagent.OAMAgentWrapperFilter.doFilter(OAMAgentWrapperFilter.java:120)
        at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
        at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:163)
        at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
        at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
        at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
        at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3730)
        at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3696)
        at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
        at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
        at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2273)
        at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179)
        at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1490)
        at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
        at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused by: javax.security.auth.login.FailedLoginException: [Security:090304]Authentication Failed: User xelsysadm javax.security.auth.login.FailedLoginException: [Security:090302]Authentication Failed: User xelsysadm denied
        at weblogic.security.providers.authentication.LDAPAtnLoginModuleImpl.login(LDAPAtnLoginModuleImpl.java:261)
        at com.bea.common.security.internal.service.LoginModuleWrapper$1.run(LoginModuleWrapper.java:110)
        at java.security.AccessController.doPrivileged(Native Method)
        at com.bea.common.security.internal.service.LoginModuleWrapper.login(LoginModuleWrapper.java:106)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:606)
        at javax.security.auth.login.LoginContext.invoke(LoginContext.java:784)
        at javax.security.auth.login.LoginContext.access$000(LoginContext.java:203)
        at javax.security.auth.login.LoginContext$4.run(LoginContext.java:698)
        at javax.security.auth.login.LoginContext$4.run(LoginContext.java:696)
        at java.security.AccessController.doPrivileged(Native Method)
        at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:695)
        at javax.security.auth.login.LoginContext.login(LoginContext.java:594)
        at com.bea.common.security.internal.service.JAASLoginServiceImpl.login(JAASLoginServiceImpl.java:113)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:606)
        at com.bea.common.security.internal.utils.Delegator$ProxyInvocationHandler.invoke(Delegator.java:57)
        at com.sun.proxy.$Proxy16.login(Unknown Source)
        at weblogic.security.service.internal.WLSJAASLoginServiceImpl$ServiceImpl.login(WLSJAASLoginServiceImpl.java:89)
        at com.bea.common.security.internal.service.JAASAuthenticationServiceImpl.authenticate(JAASAuthenticationServiceImpl.java:82)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:606)
        at com.bea.common.security.internal.utils.Delegator$ProxyInvocationHandler.invoke(Delegator.java:57)
        at com.sun.proxy.$Proxy34.authenticate(Unknown Source)
        at weblogic.security.service.WLSJAASAuthenticationServiceWrapper.authenticate(WLSJAASAuthenticationServiceWrapper.java:40)
        at weblogic.security.service.PrincipalAuthenticator.authenticate(PrincipalAuthenticator.java:338)
        at weblogic.servlet.security.internal.SecurityModule.checkAuthenticate(SecurityModule.java:252)
        at weblogic.servlet.security.ServletAuthentication.login(ServletAuthentication.java:466)
        ... 76 more
Any help will be appreciated.
Thanks

OAM side:
How you deleted OAM server?
It seems that OAM server not uninstalled clearly.
OIM side:
Check for the OIMAuthenticator in the security->realms->myrealm in weblogic
There should be OIMAuthenticator to authenticate OIM users through the database.
Is your DefaultAuthenticator also set to Sufficient?

Is it possible to have different authentication mode for SQL Server Database Engine and corresponding SQL Server instance?

Hi,
I have installed the x64 SQL Server 2008 R2 Express with default settings and run MBSA 2.3 (using default settings too). It shows three SQL Server instances: MSSQL10_50.SQLEXPRESS, SQLEXPRESS and SQLEXPRESS (32-bit). For the first, authentication
mode is Windows, for the rest two - mixed. Here https://social.msdn.microsoft.com/Forums/sqlserver/en-US/03e470dc-874d-476d-849b-c805acf5b24d/sql-mbsa-question-on-folder-permission?forum=sqlsecurity question
about such multiple instances was asked and the answer is that "MSSQL10.TEST_DB
is the instance ID for the SQL Server Database Engine of the instance, TEST_DB", so in my case, it seems that MSSQL10_50.SQLEXPRESS is the instance ID for SQL Server Database Engine of the SQLEXPRESS instance.
I have two questions:
1) How can it be that SQL Server DB Engine instance has different authentication mode than corresponding SQL Server Instance?
2) Why 32-bit instance reported although I installed only 64-bit version?
Also, this https://social.technet.microsoft.com/Forums/security/en-US/6b12c019-eaf0-402c-ab40-51d31dce968f/mbsa-23-reporting-sql-32bt-instance-is-running-in-mixed-mode-when-it-is-set-to-integrated?forum=MBSA question seems to be related to this
issue, but there is no answer :(.
Upd: Tried on clean Windows 8 installation and Windows 7 with the same result.

Because I DO NOT want the three people who will be having access to the production SQL Server to also have access to the primary host ProductionA. Since I have to allow them to RDC into the box to manage the SQL Server, I figure why not create
a separate VM for each one of them and they can RDC into those instead.
Does this make any sense?
Any tips are greatly appreciated. The main reason for doing this is because the three people who will be accessing the box, I need to isolate each one of them and at the same time keep them off of the primary ProductionA.
Thanks for your help.
M
Hello M,
Since you dont want the 3 guys to have access to Production machine A.You can install SQL Server client .By client i mean SQL server management studio(SSMS) on there local desktop and then create login for them in SQL Server.Open port on which your SQL server
is running for three of the machines so that they can connct.Now with SSMS installed on each machine each can connect to SQL server from there own machine.
I would also like you to be cautious with giving Sysadmin privilege to all three of them ,first please note down what task they would do and then decide what rights to be provided.
Your option will also work but you need to create 3 VM for that .Which is more tedious task.
Hope this helps
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

Enterprise authentication Mode Login error

Similar Messages

Maybe you are looking for