Upgrade of 10.3.6 WLS with ADF libs to 12.1.3

Hi All,
I am migrating a 10.3.6 environment which has ADF libraries installed. So:
1). I installed 12.1.3  ADF runtime on my 12.1.3 environment.
2). Then ran reconfig.sh to upgrade. I am getting below errors; ************
Preparing...
Reconfiguring Core WLS infrastructure...
Reading Domain...
Selecting Reconfiguration Templates...
Applying Reconfiguration Templates...
Creating Domain View...
Validating Domain...
The upgraded domain is valid! Reconfiguration Failed! Exception: Exception: CFGFWK-60953: An application or library was not relocated to the new MW home.
CFGFWK-60953: An error in the reconfiguration templates resulted in the following deployments being left in the original MW home:
state-management-provider-memory-rar-12.1.3
wsil-wls#12.1.3.0.0
DMS Application#12.1.3.0.0
coherence-transaction-rar
[email protected]
[email protected]
[email protected]
[email protected]
emcore_jar
[email protected]
[email protected]
[email protected]
emcorecommon_jar
emcoreconsole_jar
emcorepbs_jar
emcoreclient_jar
em_sdkcore_ppc_public_pojo_jar
em_core_ppc_pojo_jar 
CFGFWK-60953: Correct the reconfiguration templates ************ 
ANy ideas are appreciated thanks

Did you install the 12.1.3 infrastructure?
Are you following any upgrade documentation?
Documentation such as :
Upgrading to the Oracle Fusion Middleware Infrastructure 12c (12.1.3) - Contents

Similar Messages

  • JDeveloper 12c & Standalone WLS w/ADF Runtime 12.1.2

    My question is related to setting up WLS with ADF...
    Has anyone tried setting up WLS 12.1.2 with ADF Runtime 12.1.2? I cannot seem to successfully deploy a simple ADF 12c app against the new standalone WLS container.
    First, I installed WLS 12.1.2 (no coherence) followed by ADF Runtime 12.1.2.
    When creating a new domain, I setup the domain with default option (nothing checked-EM,JRF,etc..)
    Upon deploying a simple app with a page, I receive the following error:
    [02:32:43 PM] [Deployer:149193]Operation "deploy" on application "ADF12cTest" has failed on "AdminServer".
    [02:32:43 PM] [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application ADF12cTest on AdminServer.: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: adf.oracle.domain, exact-match: false].
    [02:32:43 PM] weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: adf.oracle.domain, exact-match: false]
    [02:32:43 PM] Deployment cancelled.
    [02:32:43 PM] ----  Deployment incomplete  ----.
    [02:32:43 PM] Remote deployment failed (oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer)
    However, if I check off EM,JRF. I am asked to create a DB connection!
    http://i.imgur.com/fPPaw7t.jpg
    I am not interested in using Coherence at the moment, is there an option to just setup a standalone WLS 12c server with ADF 12.1.2 runtime?
    Also, does the "Coherence" option imply that ADF Runtime will be included in the domain libs?

    Shay, that was the doc I was following, seems like I might have to go another direction now that Brian has confirmed the additional JRF requirements associated with wls 12c. I'm not going to start using technology which I do not understand or have a need yet...so paddling backwards with some wishful thinking, I attempted to run the ADF 12c infrastructure installer against a wls 10.3.6 setup, which results in:
    http://i.imgur.com/u3dv5Km.jpg
    That pretty much dashes my hopes for an easy install...so moving on.
    JDev/ADF 12c is certified for wls 10.3.5+, are there any documentation on how to upgrade ADF Runtime 11.1.2 on WLS 10.3.6 to ADF 12c (perhaps via OPatch)?

  • ADF Libs with Eclipse Hibernate/Spring Configuration

    Hi
    I have been using Spring and Hibernate in our projects.
    Now we plan to use ADF in the same project.
    I would like to know whether the JDeveloper 11g R2 with ADF Libs conflict with Eclipse Spring/Hibernate Configuration.
    Thanks in advance..
    Regards,
    Bala

    here is one how to use spring, and for Hibernate, since JPA support is there shouldn't be a problem
    http://technology.amis.nl/blog/765/spring-and-oracle-adf-registering-a-pojo-spring-jdbc-based-business-service-as-data-control.
    As far as eclipse is concerned, oracle has its only flavor of eclipse but i doubt it has the full features of ADF
    http://www.oracle.com/technetwork/developer-tools/eclipse/downloads/index.html
    Edited by: in the line of fire on Jul 26, 2011 12:11 PM

  • Upgrading WLS+ADF to 11.1.1.6: problem with ADF libraries

    Hi,
    I'm upgrading a standalone ADF environment (on RHEL5 64-bit) from 11.1.1.2.0 to 11.1.1.6.0. I followed note 1408663.1 "How to upgrade a WLS domain extended with ADF libraries" so first upgraded WLS to 10.3.6., then uninstalled Application Developer and finally installed the new ADF Runtime.
    When I ran the upgradeJRF command in wlst for my existing domain, I got a listing of 11.1.1.2.0 targets and no mention of 11.1.1.6.0 (no error messages either, though). Starting the servers I'm still seeing deployments such as adf.oracle.domain(1.0,11.1.1.2.0) and adf.oracle.domain.webapp(1.0,11.1.1.2.0). Shouldn't these be 11.1.1.6.0 now? Also tried re-deploying my application, re-built with JDeveloper 11.1.1.6.0, but the library deployments are still on 11.1.1.2.0.
    How can I upgrade the existing domain to 11.1.1.6.0?
    Regards,
    Joonas

    hi Joonas
    Joonas Linkola wrote:
    ...Starting the servers I'm still seeing deployments such as adf.oracle.domain(1.0,11.1.1.2.0) and adf.oracle.domain.webapp(1.0,11.1.1.2.0). Shouldn't these be 11.1.1.6.0 now? ...See also the related ADFEMG JIRA issue ADFEMG-112, "ER 12834041 : ADF RUNTIME LIBRARIES DON'T SHOW THE CORRECT VERSION NUMBERS IN WLS CONFIG.XML"
    at http://java.net/jira/browse/ADFEMG-112
    (or the forum message at Re: ADF Version to be used on a FormsReports 11gR2 install )
    regards
    Jan Vervecken

  • Wls-10.3.4 AD auth failed with ADF 11.1.1.3 app after upgrade from 10.3.3

    Hi,
    i have posted same issue on wls-10.3.4 Active Directory Authentication failed after Upgrade from 10.3.3
    I'm not sure if this could be an adf or wls topic.
    we have a wls 10.3.3 Installation with ActiveDirectory authentication provider.
    Delegated authentication against AD has worked very well.
    Now we have installed wls 10.3.4 and have configured the ActiveDirectory authentication provider in the same manner.
    Users and groups are listed like before in wls console, but authentication from our running ADF application is answered with "invalid username or passwort".
    No exceptions are logged in domain or admin server logs.
    The application was developed and compiled (ojdeploy) with jdev 11.1.1.3.
    wls 10.3.4 domain is upgraded with adf 11.1.1.3 libs.
    Authenication over wls console with AD credentials also fails.
    Has anybody made same experiences or workarounds?
    Thanks in advance
    Andre

    Hi,
    you should take a look at the ADF security files , especially the jazn xml file. Try to open your PS2 application in the new Ps3 Jdev and look if there are changes to the jazn.xml.
    Or you can check the jazn data xml file in the fmwconfig folder of the config domain folder.
    and check all the authenticators if everything has the sufficient control flag.
    hope this helps

  • Problem with ADF Security / SQL Authenticator after upgrade to 11.1.1.6

    Hi,
    We have an ADF application built with JDeveloper 11.1.1.2 that's been in production for a couple of years. Now we are in the process of upgrading to 11.1.1.6 so I have upgraded WLS and ADF in a test environment and re-deployed the application there. The application uses users and groups from database using SQL Authenticator configured in WLS. This worked fine in the old version but now after the upgrade we can't log in with credentials from the database. I can log in if I add a user to the default authenticator. We didn't touch any of the authenticator settings or security realm configurations during the upgrade. Both authenticators are marked as SUFFICIENT, as they have always been.
    Has something changed in the way SQL Authenticator is used since 11.1.1.2? What could be the problem?
    Regards,
    Joonas

    Answering myself here: after recreating the SQL Authenticator and the ADF Security configuration logins are working again. Don't know where the problem was though.

  • Migration Jdev 11.1.1.1 to Jdev 1.1.2, IDE visual problems with ADF design

    Migration Jdev 11.1.1.1 to Jdev 1.1.2, IDE visual problems with ADF design
    CONTEXT
    I’ve been working my project with Jdev11.1.1.1, when I migrate to JDev 11.1.1.2. I realized that my project didn’t compile successfully as before besides I couldn’t see the design view in a WYSIWYG mode on my JSF pages.
    I had installed (initially) in C:\oracle\Middleware Jdev 11.1.1.1 with WLS 10.3 (default in Installer)
    A couple days ago I realized about the new Jdev release JDev 11.1.1.2 and I decided to migrate because of the IDE improvements such as Bugs Solutions, Maven support, code templates, etc).
    The new version seemed to be non-compatible with WLS 10.3 because I couldn’t mount it in the same middleware so I installed the new one in C:\oracle\Middleware11g2, JDev 11.1.1.2 with WLS 10.3.1 (default in Installer).
    EXAMPLE
    I have created a new sample Project named JDev112App, it only has 1 java class, 1 ADF template and 1 JSPx to show the errors and differences between releases of the IDE… However, I also have added the screenshots of the Project in each IDE, also I have included a screenshot of my real project (Business App).
    NOTE. Business APP project is under subversion SVN and the migration was done successfully when JDEv 11.1.1.2 opened it (it migrated automatically).
    What should I do?? .. thanks
    Best Regards,
    Screenshot1
    http://comunidadoraclehispana.ning.com/forum/attachment/download?id=2315969%3AUploadedFi38%3A15778
    Screenshot2
    http://comunidadoraclehispana.ning.com/forum/attachment/download?id=2315969%3AUploadedFi38%3A15779
    Example APP
    http://comunidadoraclehispana.ning.com/forum/attachment/download?id=2315969%3AUploadedFi38%3A15784

    I think that the problem could be preferences/settings migration from Jdev 11.1.1.1.0 to JDev 11.1.1.2.0, because I migrated not only the application but also the JDev preferences ( "Documents&Settings...Jdeveloper..." ).
    I have installed in a new machine without previous version of Jdev the new release JDev 11.1.1.2.0 and when I deploy my test application with errors ( showed in this post ), it works fine and also the design view is correct.
    I am not SURE but I think the bug or problem could be also the preference/settings migration between JdeveloperS.
    Can anybody tell me the real reason?? How can I fix it ... I don’t want to import each of my settings manually in JDev 11.1.1.2.0 ( I mean templates, javadocs settings, connections, repositories, etc).
    Thanks in advance for your help,

  • Anybody can suggest quick sample 'Hello World' with ADF/JSF to deploy on WC

    We are using JDeveloper 11g, and Web Center 10.1.3.2.
    We have Oracle Portals 10.1.2.0.2
    We want to develop a portlet and deploy it to WC 10.1.3.2 to use it in Portals 10.1.2.0.2.
    Could anybody suggest any working "Hello World' sample with ADF/JSF to deploy on WC 10.1.3.2 WSRP.
    TIA

    Just to clarify. Oracle Portal 10.12.0.2 did not support WSRP based portlets (this was introduced in 10.1.4 or Portal) as such you would need to develop a JPDK based portlet in order to use it in both Portal 10.1.2.0.2 and WebCenter. If you upgrade the portal to 10.1.4 you will be able to use a WSRP 1.0 based portlet in both products (WebCenter also supports the draft WSRP2.0 extensions so make sure that you register the correct WSDL file)
    If you are trying to use JSF components within the Portlet itself you will need to use the JSF Portlet Bridge which accounts for the differences in lifecycle between JSF and WSRP.

  • Which technology to use with ADF BC to ensure LUW

    Hi all.
    I'm working for a client and together we developing app in jDev using ADF BC and ADF Faces. App will be deployed as standalone on WLS. We need to reuse some methods from application module to outside world (another java app running on Websphere). We also need to ensure logical unit of work meaning one transaction working with two phase commit.
    After a lot of reading i came up with a solution using EJB along with ADF BC. Problem is that client wants only EJB 3.0 but jDev supports only 2.1. I spoke with Frank and he said that moving or supporting EJB 3.0 isn't gonna be soon (probably never).
    So i am looking for an alternative technology too use that supports RMII protocol like EJB does, so i can reuse code from application module.
    Any suggestions are welcome.

    Hi Frank.
    How can i then reuse code that i have written in application module. We have a couple of houndred tables that are build with ADF BC. I think it's not fancy to rewrite whole code just to use EJB 3.0 in a seperate project.
    Maybe there is a a way too create some kind of wrapper for EJB 3.0 to work along with ADF BC.
    Edited by: user5866800 on 27.9.2011 0:26
    Edited by: user5866800 on 27.9.2011 0:27

  • ClassNotFoundException when deploying to WLS with new JDev 11g patch

    I installed WLS and patched WLS with the new ADF lib ,installed the new jdev 11g , everything went well
    but when I want to deploy an application to the WLS I got this error .
    java.lang.ClassNotFoundException: oracle.adf.share.weblogic.listeners.ADFApplicationLifecycleListener
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Class.java:247)
    at weblogic.application.internal.flow.BaseLifecycleFlow$CreateListenerAction.run(BaseLifecycleFlow.java:135)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(Unknown Source)
    Truncated. see log file for complete stacktrace
    >
    I had to comment out listerner-class ientry n the weblogic-application.xml, then it works.
    <?xml version = '1.0' encoding = 'windows-1252'?>
    <weblogic-application xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/weblogic-application.xsd" xmlns="http://www.bea.com/ns/weblogic/weblogic-application">
    <!-- <listener>
    <listener-class>oracle.adf.share.weblogic.listeners.ADFApplicationLifecycleListener</listener-class>
    </listener>
    -->
    <library-ref>
    <library-name>adf.oracle.domain</library-name>
    </library-ref>
    </weblogic-application>

    Hi,
    as read in this thread : Re: Always fail to deploy to server when (Create a Simple EJB Session Bean )
    >
    This is a known JDeveloper 11g bug. If you look into the packaged EAR file, JDeveloper inserts some entries into the weblogic-application.xml file to register some listeners to perform some internal tasks it needs to deal with.
    The issue is that these classes are part of the ADF runtime and installed as part of the provided ADF domain. They are not provided as part of a standard WLS installation. Thus when you deploy a JDeveloper 11g packaged application to a non ADF augmented WLS 10.3 instance, you get a Classloading error on deployment because the specific listener-classes are not available.
    The relevant bug # for this is:
    BUG#7487416
    EAR FILE PACKAGING SETS FIXED DEPENDENCY ON
    JPSAPPLICATIONLIFECYCLELISTENER
    I believe a fix for this will be provided in the first patchset for JDeveloper 11g.
    In the meantime, if you want to workaround it, extract the weblogic-application.xml file from the EAR file, manually remove the listener entries, put the modified file back into the EAR file and then deploy it.
    -steve-
    >
    It solved the problem for me.
    But you should now get another problem, like some of us on this forum : ADFLogger will be missing. If so, please report to this thread for helping us : Standalone WLS server instance deployment failure - missing ADFLogger
    Regards.
    Luc-

  • Does Weblogic 12.1.2 come with ADF Runtime 12.1.2?

    Cross posting my question from the general section:
    I would like to know if WLS 12.1.2 already comes with ADF Runtime 12.1.2.
    In another words, if I install a standalone production WLS 12.1.2, can I deploy and run an ADF application developed with JDeveloper 12c?
    https://forums.oracle.com/thread/2559377

    I'm leaning towards no as the standard "WLS" install folder doubled in size upon installing ADF Runtime.

  • Jar file import problem with ADF application

    Hi Everyone,
    I am using Jdev 11g with integrated WLS. I have an ADF application and is trying to integrate JasperReport in it. I added the JasperReport JAR file in the project properties -> Libraries and Classpath, and checked it for "export" and "Deployed by Default'. I have my JasperReport codes in my managed bean
    as follows
    +public String cb1_action() {+
    +try {+
    +JasperDesign design = JRXmlLoader.load("C:/JDeveloper/mywork/ReentryApplication/ViewController/public_html/jasper/testReport.jrxml");+
    +JasperReport report = JasperCompileManager.compileReport(design);+
    +....+
    +}+
    +}+
    I am able to compile the managed bean class successfully. However when I run the application, I got a stack of errors like this,
    +[2009-10-08T11:31:59.910-04:00] [DefaultServer] [ERROR] [] [javax.enterprise.resource.webcontainer.jsf.application] [tid: [ACTIVE].ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: test123] [ecid: 0000IGollZuB5EirL4YBUA1AnVop00000L,0] [APP: ReentryApplication] java.lang.RuntimeException: net.sf.jasperreports.engine.JRException: Errors were encountered when compiling report expressions class file:[[+
    +C:\Documents and Settings\MISSP29\Application Data\JDeveloper\system11.1.1.1.33.54.07\DefaultDomain\testReport_1255015914097_607807.java:4: package net.sf.jasperreports.engine does not exist+
    +import net.sf.jasperreports.engine.*;+
    +....+
    It appears that the JAR file is not picked up at the runtime correctly. I tried a simple Main class with the same codes and JAR file added, it works fine. Does anyone know what I am missing within the ADF application?
    Any helps would be appreciated.
    Thanks,
    John
    Edited by: john wang on Oct 8, 2009 9:24 AM

    Timo,
    Thanks you for your prompt response.
    1. I checked The following folder (I assume this is where it supposes to be). The JAR file is there.
    C:\Documents and Settings\MISSP29\Application Data\JDeveloper\system11.1.1.1.33.54.07\o.j2ee\drs\ReentryApplication\ReentryApplication-ViewController-webapp\WEB-INF\lib
    2. I did not do anything about deployment descriptor. Since I run my application within JDev integrated WLS, I did not do anything about deployment setting. Do I need do something with deployment descriptor if I want to import additional JAR files here? With my experience with 10g, to add a JAR file within JDev, all I need to do is to add it through project properties ->libraries.
    3. I agree with your absolute path comment. This is a test of how JasperReport works with ADF application. I will work it out later.
    Thanks,
    -John

  • Issue with SharePoint foundation 2010 to use Claims Based Auth with Certificate authentication method with ADFS 2.0

    I would love some help with this issue.  I have configured my SharePoint foundation 2010 site to use Claims Based Auth with Certificate authentication method with ADFS 2.0  I have a test account set up with lab.acme.com to use the ACS.
    When I log into my site using Windows Auth, everything is great.  However when I log in and select my ACS token issuer, I get sent, to the logon page of the ADFS, after selected the ADFS method. My browser prompt me which Certificate identity I want
    to use to log in   and after 3-5 second
     and return me the logon page with error message “Authentication failed” 
    I base my setup on the technet article
    http://blogs.technet.com/b/speschka/archive/2010/07/30/configuring-sharepoint-2010-and-adfs-v2-end-to-end.aspx
    I validated than all my certificate are valid and able to retrieve the crl
    I got in eventlog id 300
    The Federation Service failed to issue a token as a result of an error during processing of the WS-Trust request.
    Request type: http://schemas.xmlsoap.org/ws/2005/02/trust/RST/Issue
    Additional Data
    Exception details:
    Microsoft.IdentityModel.SecurityTokenService.FailedAuthenticationException: MSIS3019: Authentication failed. ---> System.IdentityModel.Tokens.SecurityTokenValidationException:
    ID4070: The X.509 certificate 'CN=Me, OU=People, O=Acme., C=COM' chain building failed. The certificate that was used has a trust chain that cannot be verified. Replace the certificate or change the certificateValidationMode. 'A certification chain processed
    correctly, but one of the CA certificates is not trusted by the policy provider.
    at Microsoft.IdentityModel.X509CertificateChain.Build(X509Certificate2 certificate)
    at Microsoft.IdentityModel.Tokens.X509NTAuthChainTrustValidator.Validate(X509Certificate2 certificate)
    at Microsoft.IdentityModel.Tokens.X509SecurityTokenHandler.ValidateToken(SecurityToken token)
    at Microsoft.IdentityModel.Tokens.SecurityTokenElement.GetSubject()
    at Microsoft.IdentityServer.Service.SecurityTokenService.MSISSecurityTokenService.GetOnBehalfOfPrincipal(RequestSecurityToken request, IClaimsPrincipal callerPrincipal)
    --- End of inner exception stack trace ---
    at Microsoft.IdentityServer.Service.SecurityTokenService.MSISSecurityTokenService.GetOnBehalfOfPrincipal(RequestSecurityToken request, IClaimsPrincipal callerPrincipal)
    at Microsoft.IdentityServer.Service.SecurityTokenService.MSISSecurityTokenService.BeginGetScope(IClaimsPrincipal principal, RequestSecurityToken request, AsyncCallback callback, Object state)
    at Microsoft.IdentityModel.SecurityTokenService.SecurityTokenService.BeginIssue(IClaimsPrincipal principal, RequestSecurityToken request, AsyncCallback callback, Object state)
    at Microsoft.IdentityModel.Protocols.WSTrust.WSTrustServiceContract.DispatchRequestAsyncResult..ctor(DispatchContext dispatchContext, AsyncCallback asyncCallback, Object asyncState)
    at Microsoft.IdentityModel.Protocols.WSTrust.WSTrustServiceContract.BeginDispatchRequest(DispatchContext dispatchContext, AsyncCallback asyncCallback, Object asyncState)
    at Microsoft.IdentityModel.Protocols.WSTrust.WSTrustServiceContract.ProcessCoreAsyncResult..ctor(WSTrustServiceContract contract, DispatchContext dispatchContext, MessageVersion messageVersion, WSTrustResponseSerializer responseSerializer, WSTrustSerializationContext
    serializationContext, AsyncCallback asyncCallback, Object asyncState)
    at Microsoft.IdentityModel.Protocols.WSTrust.WSTrustServiceContract.BeginProcessCore(Message requestMessage, WSTrustRequestSerializer requestSerializer, WSTrustResponseSerializer responseSerializer, String requestAction, String responseAction, String
    trustNamespace, AsyncCallback callback, Object state)
    System.IdentityModel.Tokens.SecurityTokenValidationException: ID4070: The X.509 certificate 'CN=Me, OU=People, O=acme., C=com' chain building
    failed. The certificate that was used has a trust chain that cannot be verified. Replace the certificate or change the certificateValidationMode. 'A certification chain processed correctly, but one of the CA certificates is not trusted by the policy provider.
    at Microsoft.IdentityModel.X509CertificateChain.Build(X509Certificate2 certificate)
    at Microsoft.IdentityModel.Tokens.X509NTAuthChainTrustValidator.Validate(X509Certificate2 certificate)
    at Microsoft.IdentityModel.Tokens.X509SecurityTokenHandler.ValidateToken(SecurityToken token)
    at Microsoft.IdentityModel.Tokens.SecurityTokenElement.GetSubject()
    at Microsoft.IdentityServer.Service.SecurityTokenService.MSISSecurityTokenService.GetOnBehalfOfPrincipal(RequestSecurityToken request, IClaimsPrincipal callerPrincipal)
    thx
    Stef71

    This is perfectly correct on my case I was not adding the root properly you must add the CA and the ADFS as well, which is twice you can see below my results.
    on my case was :
    PS C:\Users\administrator.domain> $root = New-Object System.Security.Cryptography.X509Certificates.X509Certificate2("C:\
    cer\SP2K10\ad0001.cer")
    PS C:\Users\administrator.domain> New-SPTrustedRootAuthority -Name "domain.ad0001" -Certificate $root
    Certificate                 : [Subject]
                                    CN=domain.AD0001CA, DC=domain, DC=com
                                  [Issuer]
                                    CN=domain.AD0001CA, DC=portal, DC=com
                                  [Serial Number]
                                    blablabla
                                  [Not Before]
                                    22/07/2014 11:32:05
                                  [Not After]
                                    22/07/2024 11:42:00
                                  [Thumbprint]
                                    blablabla
    Name                        : domain.ad0001
    TypeName                    : Microsoft.SharePoint.Administration.SPTrustedRootAuthority
    DisplayName                 : domain.ad0001
    Id                          : blablabla
    Status                      : Online
    Parent                      : SPTrustedRootAuthorityManager
    Version                     : 17164
    Properties                  : {}
    Farm                        : SPFarm Name=SharePoint_Config
    UpgradedPersistedProperties : {}
    PS C:\Users\administrator.domain> $cert = New-Object System.Security.Cryptography.X509Certificates.X509Certificate2("C:\
    cer\SP2K10\ADFS_Signing.cer")
    PS C:\Users\administrator.domain> New-SPTrustedRootAuthority -Name "Token Signing Cert" -Certificate $cert
    Certificate                 : [Subject]
                                    CN=ADFS Signing - adfs.domain
                                  [Issuer]
                                    CN=ADFS Signing - adfs.domain
                                  [Serial Number]
                                    blablabla
                                  [Not Before]
                                    23/07/2014 07:14:03
                                  [Not After]
                                    23/07/2015 07:14:03
                                  [Thumbprint]
                                    blablabla
    Name                        : Token Signing Cert
    TypeName                    : Microsoft.SharePoint.Administration.SPTrustedRootAuthority
    DisplayName                 : Token Signing Cert
    Id                          : blablabla
    Status                      : Online
    Parent                      : SPTrustedRootAuthorityManager
    Version                     : 17184
    Properties                  : {}
    Farm                        : SPFarm Name=SharePoint_Config
    UpgradedPersistedProperties : {}
    PS C:\Users\administrator.PORTAL>

  • Upgrade ERP database 11g and ATG7 with SSO integation

    Please let us know how to Perform Upgrade ERP database 11g and ATG7 with SSO integation .
    Regards .

    We have completed to upgrade ERP database from 9.2.0.6 to 11.2.0.1 and also apply ATG 7 on Test instance.
    And user finish testing , there is no issue after upgrade and application can work as normal.
    On Test instance we didn't implement Single Sign On
    But on Production we have Single Sign ON.
    Now we plan to upgrade on Production instance. But we afraid that we will found any issue on Production relate to SSO. Becase we don't have a chance to test it.
    My question is:
    Are there any spacial step we need to do if we have implemented SSO After upgrade DB 11g and ATG 7?

  • Help required with ADFS 3.0 client certificate authentication

    Hi,
    I am currently working on integrating ADFS 3.o for Single Sign On to some 3rd party services along with PKI solution. The basic requirement is that I should be able to choose client authentication certificate as an authentication method in ADFS and then
    federate user credentials to 3rd party trust for single-sign-on.
    I had done this successfully with ADFS 2.0 and that setup is working fine. I have the setup as ADFS 3.0 client authentication method enabled. When I open browser to logon, the ADFS 3.0 page displays a message as "Select a certificate that you want to
    use for authentication. If you cancel the operation, please close your browser and try again." but the certificates are not displayed for selection.
    The certificates are valid and have valid chaining to CA. Could someone help me resolve this issue?
    Thanks!
    -Chinmaya Karve

    Hi Yan,
    Thanks for your response. I have gone through the posts that you have suggested, and my setup looks pretty much as expected.
    So, as I mentioned earlier, I have 2 parallel setups with 3rd party service(SalesForce). Once of them is running ADFS 2.0 and another one has ADFS 3.0. I can logon to the third-party services, from both the setups using username/format. I can logon to SF
    using client authentication certificate from ADFS 2.0 setup, but from the same client machine, when I try to logon SF via ADFS 3.0, the browser just does not pick up any certificate. The page just shows message of "Select a certificate that you want to use
    for authentication. If you cancel the operation, please close your browser and try again.".
    I have checked the browser, and it has the right certificates. Also, the same browser/machine is used to logon to SF through ADFS 2.0 via client certificate, which works just fine !
    I am really confused now, as to whose issue this really is...
    Just to confirm, I am using Certificate Authentication from ADFS 3.0 Authentication Methods for both Intranet and Extranet.
    Any suggestion or inputs where I could have gone wrong in the setup?
    Thanks!

Maybe you are looking for