WebLogic 10gR3 and Windows Integrated Authentication

Hi:
I have an intranet web application running on WebLogic 10gR3 and would like to make use of the Windows Integrated Authentication (SSO, SPNEGO, Active Directory) so that the intranet users don't have to log in to access the web application.
In weblogic, I've managed to create an ActiveDirectoryAuthenticator and can see all the users and groups from Active Directly. Also created a NegotiateIdentityAsserter with both WWW-Authenticate.Negotiate and Authorization.Negotiate options.
When I set the web.xml login-config to BASIC, the browser shows the login dialog and authentication happens through AD. I've changed the login-config to CLIENT_CERT as suggested by the documentation:
<login-config>
<auth-method>CLIENT-CERT</auth-method>
</login-config>but I'm getting the following error:
Error 401--Unauthorized
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.4.2 401 Unauthorized
The request requires user authentication. The response MUST include a
WWW-Authenticate header field (section 14.46) containing a challenge
applicable to the requested resource. The client MAY repeat the request
with a suitable Authorization header field (section 14.8). If the request
already included Authorization credentials, then the 401 response indicates
that authorization has been refused for those credentials. If the 401
response contains the same challenge as the prior response, and the user
agent has already attempted authentication at least once, then the user
SHOULD be presented the entity that was given in the response, since
that entity MAY include relevant diagnostic information. HTTP access
authentication is explained in section 11.Help is highly appreciated
Albert
Edited by: albertattard on Jul 13, 2009 3:40 PM
Edited by: albertattard on Jul 13, 2009 3:42 PM

Similar Messages

SSRS and SharePoint Integration Authentication Issue

We recently turned on SSRS for our SharePoint 2010 Test Environment. We are using an account that has rights to SharePoint as a site collection administrator, the feature is enabled on the site collection and site level, it has access to the SQL instance
to pull the reports. The report config file specifies NTLM authentication. It acts as if it will configure and goes through the SP Central Administration steps successfully. When I try to deploy a report, I receive the following error:
Exception encountered for SOAP method GetSystemProperties: System.Net.WebException: The request failed with HTTP status 401: Unauthorized.     at Microsoft.SqlServer.ReportingServices2010.RSConnection2010.SetConnectionProtocol()
at Microsoft.SqlServer.ReportingServices2010.RSConnection2010.SoapMethodWrapper`1.ExecuteMethod(Boolean setConnectionProtocol) 1afe9dfd-9846-4194-bddf-fcb0ded634be
06/14/2012 15:37:43.03 w3wp.exe (0x1E78)                       0x1754 SQL Server Reporting Services SOAP Client Proxy
0000 High    Exception encountered for SOAP method GetSystemProperties: System.Net.WebException: The request failed with HTTP status 401: Unauthorized.     at Microsoft.SqlServer.ReportingServices2010.RSConnection2010.SetCo
If I turn on trusted accounts, it works, but then it argues when the report loads because our reports use windows integrated authentication. We would prefer to have windows integrated authentication to control who can see reports by their
login name. Any ideas? I feel like I have exhausted options.

Can you please elaborate on how to avoid using Kerberos and use the Secure Store to access our external SQL data? In our test environment, we have SharePoint 2013 Ent, SQL 2012 Ent. I am trying to use PowerView to access a Direct Query data model created
in SSAS tabular mode. My connection from SharePoint to the model is successful but fails with a reporting service error:
Cannot create a connection to data source 'EntityDataSource'.
<detail><ErrorCode xmlns="rsErrorOpeningConnection</ErrorCode><HttpStatus">http://www.microsoft.com/sql/reportingservices">rsErrorOpeningConnection</ErrorCode><HttpStatus xmlns="400</HttpStatus><Message">http://www.microsoft.com/sql/reportingservices">400</HttpStatus><Message
xmlns="Cannot">http://www.microsoft.com/sql/reportingservices">Cannot create a connection to data source 'EntityDataSource'.</Message><HelpLink xmlns="http://go.microsoft.com/fwlink/?LinkId=20476&EvtSrc=Microsoft.ReportingServices.Diagnostics.Utilities.ErrorStrings&EvtID=rsErrorOpeningConnection&ProdName=Microsoft%20SQL%20Server%20Reporting%20Services&ProdVer=11.0.3000.0</HelpLink><ProductName">http://www.microsoft.com/sql/reportingservices">http://go.microsoft.com/fwlink/?LinkId=20476&EvtSrc=Microsoft.ReportingServices.Diagnostics.Utilities.ErrorStrings&EvtID=rsErrorOpeningConnection&ProdName=Microsoft%20SQL%20Server%20Reporting%20Services&ProdVer=11.0.3000.0</HelpLink><ProductName
xmlns="Microsoft">http://www.microsoft.com/sql/reportingservices">Microsoft SQL Server Reporting Services</ProductName><ProductVersion xmlns="11.0.3000.0</ProductVersion><ProductLocaleId">http://www.microsoft.com/sql/reportingservices">11.0.3000.0</ProductVersion><ProductLocaleId
xmlns="1033</ProductLocaleId><OperatingSystem">http://www.microsoft.com/sql/reportingservices">1033</ProductLocaleId><OperatingSystem xmlns="OsIndependent</OperatingSystem><CountryLocaleId">http://www.microsoft.com/sql/reportingservices">OsIndependent</OperatingSystem><CountryLocaleId
xmlns="1033</CountryLocaleId><MoreInformation">http://www.microsoft.com/sql/reportingservices">1033</CountryLocaleId><MoreInformation xmlns="<Source>Microsoft.ReportingServices.ProcessingCore</Source><Message">http://www.microsoft.com/sql/reportingservices"><Source>Microsoft.ReportingServices.ProcessingCore</Source><Message
msrs:ErrorCode="rsErrorOpeningConnection" msrs:HelpLink="http://go.microsoft.com/fwlink/?LinkId=20476&EvtSrc=Microsoft.ReportingServices.Diagnostics.Utilities.ErrorStrings&EvtID=rsErrorOpeningConnection&ProdName=Microsoft%20SQL%20Server%20Reporting%20Services&ProdVer=11.0.3000.0"
xmlns:msrs="Cannot">http://www.microsoft.com/sql/reportingservices">Cannot create a connection to data source 'EntityDataSource'.</Message><MoreInformation><Source>Microsoft.AnalysisServices.AdomdClient</Source><Message></Message><MoreInformation><Source>mscorlib</Source><Message>Access
is denied.
</Message></MoreInformation></MoreInformation></MoreInformation><Warnings xmlns="http://www.microsoft.com/sql/reportingservices" /></detail>

JavaMail Exchange Server Windows Integrated Authentication

I need to send an email using Java Mail by Exchange Server that uses Windows Integrated Authentication.
Is it possible? If so how?
(I read some old posts and I get some info but I have to sure is it possible or not just sending mail)

Hi, jeff81.
I had same problem with Win2003 server. Try this:
Start -> Settings -> Control Panel -> Administrative Tools -> Services
then select "PROPERTIES/LOGON" for necessary service.
Change "Local System account" to your user account.
Make sure that user account have necessary grants.
ps. sorry my poor english :(

Exchange 2013 CU1 Outlook Web App LogOff with Basic or Windows Integrated Authentication

Hi all,
Exchange 2013 CU1 has a new OWA LogOff behaviour when Basic or Windows Integrated Authentication is configured. When clicking the LogOff Button you receive the message "Close All your Browser Windows.." but OWA does not sign out. This is not the
case when using Formbased Authentication...
The problem in our case is the OWA publishing over the Internet via TMG. When publishing via TMG, only Basic and NTLM authentication is supported. This means you have to change the Authentication for the OWA Virtual Directory to basic or Windows Integrated.
OK so far, now we can use the TMG Authentication Form. but... TMG is not able to Catch the OWA LogOff. So we will still receive "Close all your Browser Settings.." and no log out from OWA.
It is a known issue that TMG cannot catch the OWA Logoff with the Exchange 2013 CU1 Release..So my Question:
Does anyone get that "Real LogOut" fixed via TMG or directly on the CAS Server for Exchange 2013 CU1?
I know another possibility is to activate Form Based Authentication on the CAS Servers and external users directly authenticate against the CAS Server without pre-authentication at TMG Level, but this of course does not provide the highest security
we can have.

Hi SLShare,
As far as I know, if there is no TMG involved, with Exchange 2013 when the user signs out of mail, the authentication tokens are cleared and the user will be presented with the
Login Screen. There will not be a need to click on "Close Window" or any other pop ups that may appear.
Therefore, you may ask the TMG forum about this question and see whether there are still some other workaround we can temporary bypass this issue. For your convenience:
Forefront TMG and ISA Server Forum - TechNet - Microsoft
http://social.technet.microsoft.com/Forums/forefront/en-US/home?forum=Forefrontedgegeneral
Thanks,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Windows Integrated Authentication Help From Middle Tier

We are trying to enable single sign-on using Windows Integrated Authentication so that the user does not have to enter a username or password, they just get logged in automatically. I created the current Oracle account on the database and it works just fine when I try to connect from my local computer to the database. Our problem is that our application calls an application that runs as a Windows services on the middle tier, and so it gets an invalid username/password error. I can see in the audit logs that it is trying to connect to the database as NT AUTHORITY\ANONYMOUS LOGON.
The client, middle tier, and database are all Windows based operating systems. The applications is a .Net application and we turned on Impersonation which we read will help pass the client OS user to middle tier so that the application runs as them. And that appears to be working correctly. Again we can get this working when we host the windows service locally, it just wont work when it is hosted on the middle tier. Any ideas how to get this to work?
Oracle version 11.2.0.2 and 11.2.0.3
Windows Server 2008 R2

Hi, jeff81.
I had same problem with Win2003 server. Try this:
Start -> Settings -> Control Panel -> Administrative Tools -> Services
then select "PROPERTIES/LOGON" for necessary service.
Change "Local System account" to your user account.
Make sure that user account have necessary grants.
ps. sorry my poor english :(

Windows Integrated Authentication on an ABAP data source

Dear Experts,
I have to implement Windows Integrated Authentication in my portal. By using Kerberos & SPNEGO, we can implement very easily if portal user id & windows (ADS) user id is same. But my scenario is windows id & portal id is different & data source is already configured as ABAP. Can you suggest me how we can achieve this requirement.
Regards,
VENU

Hi,
isnt the property krb5principalname used to define the mapping of the user ID when you cannot use the AD standard samaccountname?
I think that the mapped user ID (as provided by krb5principalname) must be identically with the ABAP userID. When the ABAP user ID isn't present in the LDAP information, SSO won't be possible. Somehow he needs to publish the ABAP user ID into the AD.
SAP Help:
http://help.sap.com/SAPHELP_NW70EHP1/helpdata/EN/43/4c363ac31e30f3e10000000a11466f/frameset.htm
http://help.sap.com/SAPHELP_NW70EHP1/helpdata/EN/43/4c3725aeaf30b4e10000000a11466f/frameset.htm
br,
Tobais

JAX-WS web service client and Windows integrated Security authentication

I am currently developing a JAX-WS web service client running on WebLogic 10.3.2.0. The client is connecting to exchange web service running on IIS.
Everything works well when EWS is configured with Http basic authentication.
The problems started when I changed the autentication method on EWS from Http basic authentication to Windows integrated Security authentication.
The client is then unable to authenticate to the web service. Every request made to EWS returns with the message : Invalid HTTP server response [401] - Unauthorized.
I tried using an authenticator like this one:
static class RetrieveWSDLAuthenticator extends Authenticator
private String username, password;
public RetrieveWSDLAuthenticator(String user, String pass)
username = user;
password = pass;
@Override
protected PasswordAuthentication getPasswordAuthentication()
return new PasswordAuthentication(username, password.toCharArray());
and setting it as the default authenticator :
Authenticator.setDefault(new MyAuthenticator("username", "password"));
but the method getPasswordAuthentication() was not even called.
Is there a way to make a JAX-WS client works with Windows integrated Security ?

WIS is not suppported on WLS JAX-WS. You'll need to use other authentication mechanisms such as http basic (which you tried already), or message-level security such as UNT, or SAML.
Regards,
Pyounguk

WIndows 7 and Windows 2008 authentication failed in Windows 2003 Domain

Hi,
We have Domain with Windows 2003 and recently Windows 2008 Doamin controllers also added.
We are facing authentication failure for Windows 7 and Windows 2008 Domain members when user is trying to login.
Schema Master is on Windows 2003 and remaining roles on Windows 2008 Domain controller.
Windows XP clients login is working fine.
Problem si for Windows 7 and Windows 2008 Domain members login.
Any hint/solution will be really great help.
Pls share if you have any solutions.
Regards:Mahesh

Hi,
I found some more details about issue
Below are the events getting generated. It looks like due to encryption mismatch with Windows 2003 Domain and Windows7 and Windows 2008 clients. However i am looking for solution if someone tested this case.
Event Type:        Error
Event Source:    KDC
Event Category:                None
Event ID:              26
Date:                     08/06/2014
Time:                     9:41:04 AM
User:                     N/A
Computer:          AAAAAA
Description:
While processing an AS request for target service krbtgt, the account ADDADA$ did not have a suitable key for generating a Kerberos ticket (the missing key has an ID of 2). The requested etypes were 17. The accounts
available etypes were 23 -133 -128 3 -140.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Event Type:        Error
Event Source:    Kerberos
Event Category:                None
Event ID:              4
Date:                     08/06/2014
Time:                     9:34:17 AM
User:                     N/A
Computer:          AAAAAA
Description:
The kerberos client received a KRB_AP_ERR_MODIFIED error from the server ADADDFHDHDH$. The target name used was . This indicates that the password used to encrypt the kerberos service ticket is different than that on the
target server. Commonly, this is due to identically named machine accounts in the target realm (DOMAINNAME.COM), and the client realm.   Please contact your system administrator.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Regards:Mahesh

Windows Integrated Authentication to SAP R/3

Hi,
I dont know weather this issue has to be posted here or in WAS or GUI.
Is there any way to do the Integrates Windows Authentication to SAP R/3. Once the Users logs in to the Network domain adn then to SAP GUI, the User should not prompt for User id and should directlt take in to the Role Menu.
I know for Portal it is possible, but i am not sure for R/3. Please let me know if there is any documentation for the same.
Thanks & Regards
Sumanth

Sumath,
there are various variants to do so:
If your R/3 is running on Windows (and in the same / trusted domain), you can use SNC with either NTLM or Kerberos authentication
Otherwise you can log on with SAP Logon Tickets. You mentioned already that you know NTLM/Kerberos is feasible with EP. Now, if you simply integrate your R/3 systems in EP by means of SAP logon tickets you have essentially a smooth SSO for your users.
Finally, you can use ITS up to 6.20 on Windows to SSO to R/3 (the latter on not neccessarily on Windows, too). Simply setup webgui, active SAP logon tickets and configure the PAS service to use Windows authentication.
Whatever you decide on, al alternatives are a piece of cake to set up.
Regards,
Dominik

Windows Integrated Authentication & SAP Logon tickets

1) We have configured windows authentication and the IISproxy on a SPS frontend server to our SAP portal environment.
2)We have configured SAP logon tickets on the SAP portal (running on hp-ux).
3) Both the IIS server and the sap portal server exist on the same domain inside our firewall (iis_server.lsv.internal_company_name.com and sap_portal_server.lsv.internal_company_name.com)
4) A virtual URL has been created on the IIS server, http://sap_portal.external_company_name.com, using a domain alias.
5) When an authenticated user is passed from the IIS server to the SAP portal the SAP logon ticket that is created is for external_company_name.com alias rather than lsv.internal_company_name.com. This logon ticket is not accepted by any of the backend SAP systems that have been configured to except logon tickets because they all exist in the lsv.internal_company_name.com domain.
6) The portal security guide says:
"The Portal Server issues a SAP logon ticket for the Internet domain or a sub-domain of the
Portal Server only."
Given this scenario, is there some configuration that can be added to allow the use of this alias or is there a bug in the SAP portal code that needs to be addressed?

Hi,
You cannot use the external alias. You can however set SSO on the portal not to look to the total url. For example it would work if you use:
sap_portal_server.lsv.internal.company_name.com
and
sap_portal.external.company_name.com
The prerequisite here is that at least the domain name should be the same i.e. the last two parts.
Greetings,
Vincent

Weblogic.rmic and ant integration issue

I am trying to call weblogic.rmic compiler through a ant script and was
sucessful in doing so and generating the stubs and skelton for my RMI
implementation.
But i also want to pass a system property value (in the example i am passing
file=stdout using -D to java) to weblogic.rmi compiler and don't know how to
do that.
Any help will be greatly appreciated...
Thanks
Kunjan Jhaveri
781-372-3965
[email protected]
PS: Script enclosed.
<target name="local.genStubs" depends="local.compile">
<java classname="weblogic.rmic" fork="yes" failonerror="yes">
<jvmarg value="-Dfile=stdout" />
<arg value="-classpath" />
<arg value="${WL_HOME}${file.separator}lib${file.separator}weblogic.jar" />
<arg value="-d" />
<arg value="${SRCDIR}${file.separator}build${file.separator}classes" />
<arg value="com.ehealthdirect.ee.kernel.EEMutexManagerImpl" />
<classpath>
<pathelement
path="${WL_HOME}${file.separator}lib${file.separator}weblogic.jar" />
</classpath>
</java>
</target>

As far as I know, rmic doesn't know anything about a "file" system property. Is
there some reason you expect this to do something special?
Kunjan Jhaveri wrote:
I am trying to call weblogic.rmic compiler through a ant script and was
sucessful in doing so and generating the stubs and skelton for my RMI
implementation.
But i also want to pass a system property value (in the example i am passing
file=stdout using -D to java) to weblogic.rmi compiler and don't know how to
do that.
Any help will be greatly appreciated...
Thanks
Kunjan Jhaveri
781-372-3965
[email protected]
PS: Script enclosed.
<target name="local.genStubs" depends="local.compile">
<java classname="weblogic.rmic" fork="yes" failonerror="yes">
<jvmarg value="-Dfile=stdout" />
<arg value="-classpath" />
<arg value="${WL_HOME}${file.separator}lib${file.separator}weblogic.jar" />
<arg value="-d" />
<arg value="${SRCDIR}${file.separator}build${file.separator}classes" />
<arg value="com.ehealthdirect.ee.kernel.EEMutexManagerImpl" />
<classpath>
<pathelement
path="${WL_HOME}${file.separator}lib${file.separator}weblogic.jar" />
</classpath>
</java>
</target>

Weblogic agent and SAM integration

Hi all,
after configuring everything as mentioned in the documentation I'm still getting an excetion:
F:\SJS_Weblogic_9_agent_2.2\j2ee_agents\am_wl9_agent\bin>agentadmin --getUuid an
dy user sun
Failed to create debug directory
Failed to create debug directory
Failed to create debug directory
Failed to create debug directory
Failed to create debug directory
01/17/2007 01:15:37:156 PM GST: Thread[main,5,main]
DataLayer: number of retry = 3
01/17/2007 01:15:37:156 PM GST: Thread[main,5,main]
DataLayer: retry interval = 1000
01/17/2007 01:15:37:156 PM GST: Thread[main,5,main]
DataLayer: retry error codes = []
Failed to create debug directory
01/17/2007 01:15:37:203 PM GST: Thread[main,5,main]
AdminUtils: Could not initialize admin info message: Got LDAPServiceException c
ode=19
01/17/2007 01:15:37:203 PM GST: Thread[main,5,main]
Crypt.static{}: Encryptor class= com.iplanet.services.util.JSSEncryption
Exception in thread "main" java.lang.NoClassDefFoundError: org/mozilla/jss/crypt
o/KeyGenAlgorithm
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:164)
at com.iplanet.services.util.Crypt.createInstance(Crypt.java:133)
at com.iplanet.services.util.Crypt.<clinit>(Crypt.java:103)
at com.iplanet.am.util.AdminUtils.getAdminDN(AdminUtils.java:106)
at com.sun.identity.sm.SMSEntry.<clinit>(SMSEntry.java:166)
at com.sun.identity.sm.DNMapper.<clinit>(DNMapper.java:59)
at com.sun.identity.idm.AMIdentity.<init>(AMIdentity.java:135)
at com.sun.identity.agents.tools.handler.GetUniversalIdHandler.handleReq
uest(GetUniversalIdHandler.java:120)
at com.sun.identity.agents.tools.admin.AgentAdmin.dispatch(AgentAdmin.ja
va:251)
at com.sun.identity.agents.tools.admin.AgentAdmin.run(AgentAdmin.java:15
2)
at com.sun.identity.agents.tools.launch.AgentAdminLauncher.launchAdminTo
ol(AgentAdminLauncher.java:204)
at com.sun.identity.agents.tools.launch.AgentAdminLauncher.main(AgentAdm
inLauncher.java:308)
Do you where is the missing class and to which class path I should add it?
Thanks in advance

I'm getting the below exception. It seems like weblogic can't initialize the idm service. Any idea?
SSOTokenValidator: validate failed with exception
[AgentException Stack]
com.sun.identity.agents.arch.AgentException: Invalid transport string
     at com.sun.identity.agents.util.TransportToken.initializeFromString(TransportToken.java:158)
     at com.sun.identity.agents.util.TransportToken.<init>(TransportToken.java:130)
     at com.sun.identity.agents.common.SSOTokenValidator.validate(SSOTokenValidator.java:120)
     at com.sun.identity.agents.realm.AmRealm.authenticate(AmRealm.java:149)
     at com.sun.identity.agents.weblogic.v9.AmWLLoginModule.login(AmWLLoginModule.java:137)
     at weblogic.security.service.DelegateLoginModuleImpl$loginDelegateAction.run(DelegateLoginModuleImpl.java:169)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
     at weblogic.security.service.DelegateLoginModuleImpl.executePriv(DelegateLoginModuleImpl.java:121)
     at weblogic.security.service.DelegateLoginModuleImpl.login(DelegateLoginModuleImpl.java:86)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at javax.security.auth.login.LoginContext.invoke(LoginContext.java:769)
     at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186)
     at javax.security.auth.login.LoginContext$4.run(LoginContext.java:683)
     at java.security.AccessController.doPrivileged(Native Method)
     at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680)
     at javax.security.auth.login.LoginContext.login(LoginContext.java:579)
     at weblogic.security.service.PrincipalAuthenticator.authInternal(PrincipalAuthenticator.java:412)
     at weblogic.security.service.PrincipalAuthenticator.authenticate(PrincipalAuthenticator.java:352)
     at weblogic.security.service.SecurityServiceManagerDelegateImpl.doBootAuthorization(SecurityServiceManagerDelegateImpl.java:780)
     at weblogic.security.service.SecurityServiceManagerDelegateImpl.initialize(SecurityServiceManagerDelegateImpl.java:893)
     at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:775)
     at weblogic.security.SecurityService.start(SecurityService.java:133)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
Best regards

Windows Integrated Security with SSRS, Sharepoint 2013 and SSAS over http

I have the following setup and problem:
Sharepoint 2013 with SSRS in Sharepoint integrated mode
SSAS 2012 SP1 with http access (IIS + msmdpump) enabled on the same box as SSAS
Every component I have tried works fine with this (PerformancePoint, .bism connections, SSIS packages etc.), connecting over http using Kerberos and windows integrated authentication.
SSRS (.rsds) connections in Sharepoint fail a connection test when using the same http connection string + Windows integrated authentication which works for everything else. The error is: "Unsupported data format: -> Microsoft.ReportingServices.DataExtensions.AdomdTestConnectionException:
Unsupported data format:"
SQL server profiler shows that the windows username is reaching the SSAS server is all cases.
Kerberos delegation is set up for SSAS and is working.
Switching the .rsds connection to saved credentials (same user as I tried with Windows integrated auth) works fine and SQL server profile logs look the same as the Windows integrated case.
So, everything seems to work with Kerberos + http apart from SSRS ... any idea welcome. I did read that SSPI is not supported for http connections but then again, there are sites which give examples of exactly such connection strings. I can't find any
mention of this case or exact problem anywhere ...

For information, this was fixed by applying the .NET 4.5.1 patch as advised by MS support. Now http connections from integrated mode SSRS work ok.

Problems setting up WNA with OAS 10.1.2.0.2 and Windows 2008

Hi,
I am trying to set up WNA with an OAS 10.1.2.0.2 in a RHEL 4 platform. I have been able to configure Synchronization and Windows External Authentication following these steps:
http://download.oracle.com/docs/cd/B14099_19/idmanage.1012/b14085/odip_actdir003.htm#i1010999
I have also tried to configure WNA without success with those steps.
The scenario is here:
* OAS 10.1.2.0.2 infra in a RHEL 4
* Windows 2008 SP1 (only i use AD from it)
* Windows XP (client) that should be able to log in without problems when WNA is configured
How can make it work? I haven´t find any useful documentation
Thanks,
Max

Check these out:
http://www.freeoraclehelp.com/2011/09/oid-integration-with-ms-active.html
http://www.freeoraclehelp.com/2011/09/enable-ssl-for-oid-instance-of-oracle.html
http://www.freeoraclehelp.com/2011/09/oracle-password-filter-to-sync.html

SQL Server plug in and windows server 2008

Windows Server 2008
SQL Server 2008
JDBC drivers 3.0
I am trying to setup Oracle Grid to monitor the SQL Server instances and ive resolved most of the issues execpt i keep getting the following error when testing connection to SQL server
Warning
Failed to contact the target to be added. Following errors were received while testing the connection to the target. Update the properties accordingly, try Test Connection for testing the properties before saving.
1. MSSQLDetermineName_DynamicProperty - em_error=Could not connect. Error code = 0x8004100e em_error=Failed while connecting to WMI.
2. Response - Missing Properties : [provided_sql_server_name]
Ive read about the code and it says add the Microsoft namespace to WMI but then it says it only applies to SQL Server 2000.
These are my jdbc settigs:
jdbc url: jdbc:sqlserver://<servername>:1433
jdbc driver: com.microsoft.sqlserver.jdbc.SQLServerDriver
History:
i was getting other errors before regarding wrong version of SQL Server installed so i downloaded the JDBC 3.0 drivers and copied the 2 files:
sqljdbc.jar and sqljdbcr4.jar
to <oracle_agent_home>\sysman\admin\scripts\emx\microsoft_sqlserver_database
after this i got the current problems
I think it may be a permissions problem with WMI or something connected around it.

Please review the installation documentation at:
* http://download.oracle.com/docs/cd/B16240_01/doc/install.102/e16546/sqlig.htm
You will see that the sqljdbc_auth.dll needs to be copied only if you are using Windows Integrated Authentication on a 64 bit OS:
For the plug-in to establish connection to SQL Server instance using Windows Integrated Authentication mode, when deployed on a 64-bit (X64 or IA64) copy of Enterprise Manager Agent running on 64-bit Windows operating system, do the following:
Depending on the JVM version, copy the respective version of sqljdbc_auth.dll to the folder $AgentHome\sysman\jdbcdriver. If the directory does not exist, create it. The file sqljdbc_auth.dll is available as part of Type 4 Microsoft SQL Server 2005 JDBC Driver version 1.2 (after unzipping, you will find three files with same name, that is, auth\x86\sqljdbc_auth.dll, auth\x64\sqljdbc_auth.dll, and auth\ia64\sqljdbc_auth.dll)
o
For X64 version of Enterprise Manager Agent installed on X64 (Xeon or AMD) Windows systems, copy the file auth\x64\sqljdbc_auth.dll to $AgentHome\sysman\jdbcdriver (the dll file should be copied directly under the folder specified. No sub-directories should be created.)
o
For IA64 version of Enterprise Manager Agent installed on IA64 Windows systems, copy the file auth\ia64\sqljdbc_auth.dll to $AgentHome\sysman\jdbcdriver
Note:
· No manual step needs to be performed when the plug-in is deployed on 32-bit copy of Enterprise Manager Agent (running on 32-bit or 64-bit Windows).

WebLogic 10gR3 and Windows Integrated Authentication

Similar Messages

Maybe you are looking for