XMII Authentication

Hi,
I am using HTML page for login screen. user authentication is being done by xMII. So if the authentication fails then xMII page "error.jsp" appears which says "<b>Access denied Authentication required</b>". how can I get the same HTML login page again instead of xMII page if the authentication fails. So that user can retry to login without closing the browser.
Thanks,
Rajiv

Rajiv
Here u din't understand wat Jeremy said ni previous post. He said to use the Page with <b>irpt</b> extension, NOT htm extension.
That is ur application page must be xyz<b>.irpt</b> as follows:
location = "http://" + server + "/Illuminator/PortalLogin.jsp?target=/application/xyz<b>.irpt</b>&IllumLoginName=" + txtUsername.value + "&IllumLoginPassword=" + txtPassword.value + "&session=true"
Regards
Som

Similar Messages

  • XMII Applet and Authentication

    Hi,
    I have a webpage which has an applet embeded on it. I can access this webpage via a browser from the local xmii server and the applet displays correctly. Whenever I try to access it from a remote client I am getting an "Authentication Required" message where the applet should be. The rest of the page is displayed normally. Can anyone help with this.
    In the java console I am getting the following exception:
    ERROR - Error Loading Resource File for Applet_: access denied (java.util.PropertyPermission http.strictPostRedirect read)
    Authenticator::Authentication error is Authentication Required
    Thanks,
    Mahwish

    Hi Mahwish,
    I am assuming that you are using an htm or html for you web page extension.  Try changing the extension to irpt to force you to log into xMII prior to loading the page.  You could also use the URL
    http://<server name>/Illuminator/PortalLogin.jsp?target=/dir/page.htm
    To force htm or html pages to authenticate please see note 930312
    Regards,
    Jamie Cawley

  • User authentication Failed in XMII portal

    Hi,
    we are using XMII 12.0 version and deployed in SAP netweaver 2004s. We are frequently facing issue in XMII Menu page login and in SAP netweaver user management logins as "User authentication Failed". It is happening for all users suddenly. we are giving  username and password correctly but we faced the same problems. We tried with all users then also we cant able to find the probem. Every time we needs to restart the server then it works.
    What is the issue and how to resolve it?
    Regards,
    Senthil

    Hi Senthil,
    I would strongly recommend upgrading your installation.  You are on 12.0.2 and the current release is 10 service packs later.  You should upgrade to 12.0.12 before working on what is probably the original GA version from about 4 years ago.
    Regards,
    Mike

  • Calling Webservice from Netweaver Portal to SAP XMII 12.0 using SSO

    Hello,
    we have a Netweaver 2004s based Portal and a Netweaver-based SAP XMII (v12.0) System providing Webservices.
    What we try to do is to call a webservice out of the Portal EAR Application using SSO.
    SSO-Konfiguration between Portal and XMII is done and works fine. I tested this using an URL-iView, which calls a https-URL on XMII and SSO-Authentification is done in the background.
    Now I want to call a Webservice using SSO.
    Without SSO (prodiving UID/PW), the webservice-call works fine.
    In order to use SSO with Webservice, I created a "Deployable Webservice Proxy" with "HTTP-Authentication" and "use SAP Logon Ticket" turned on.
    Then I remove Login/Password from my SOAP-Request and unfortunately it doesn't work.
    What do I have to consider in addition to the topics above?
    Can you provide any useful links with tutorials, hints, documentation, ...?
    Thanks in advance
    Andreas

    > Can you please list all the options that we have in order to implement SSO for EP and SAP GUI?
    >
    > I could not find any info in regards to the advantages and disadvantages of each SSO solution. Do you have any links that gives this information?
    If you search the forum here for the terms you have used, then you will find many of them and interesting discussions about advantages and disadvantages from different views. I think that in 1 or 2 hours you will be a guru
    > I am thinking more of using Kerberos authentication for SAP GUI and using OpenSSO (Sun's product)solution for EP 7.0.
    >
    > Do you know what SSO technologies are other companies implementing these days?
    I only know which solutions I have been involved in doing the security evaluations for and implementation support.
    I don't want to do any direct or indirect comparative advertizing here, but only wanted to point out to you that there is plenty of information if you use the search. What you need to understand is that other that SAP proprietary mechanisms and newer standards based initiatives (search for 'SAML'), this is often a 3rd party vendor question (and resulting discussion...).
    If you find a solution and want to specifically discuss it here, then this can most of the time be done in a civilized way...
    Cheers,
    Julius

  • SOAP Web Service Authentication configuration

    Hello,
    I've got a little problem with Web Service authentication configuration.
    I'm working on the SAP NetWeaver CE EHP1 7.11. I also have a XMII application deployed on the server and there are some SOAP Web Services(over XMII Transactions) that require basic authentication.
    I use all Web Services in the EJB layer. So, I've generated proxy using SAP NetWeaver as a Web Service Runtime for generation. And Iuse an injection mechanism to get a service implementation:
    @WebServiceRef(name="GetBatchListService")
    private XacuteWS batchListWS;
    In this case I could use Single Service Administration application in the NetWeaver Administrator@SOA Management@Application and Scenario Communication to configure basic authentication for EVERY Web Service. And this configuration disappears after every redeploy.
    The question is how and where could I configure authentication for all web services?
    I've read a lot of documentation, but, unfortunately, I haven't found needed one. I could see 2 direction of searching now, it might help:
    1) Destination: Configure HTTP Destination or Web Service Template Destination and use it in all Web Services proxies somehow.
    2) Find Configuration way: Create a configuration group or anything else to configure all services from one screen.
    Best Regards,
    Dmitry

    Dimtris,
    If your WSDL url is pointing to the URL of the Adapter Engine as shownin the Hot to Use the SOAP adapter there is no option. You cannot add it to the SOAP Url.
    But, if you change the SOAP Url to the Url shown in this blog by Stefan Grube then you can add the user id and pasword to the url by adding sap- user=userid and sap-password = password.
    The optin shown ion the blog by Grube can be used as long as you do not have to use SOAP attachments and in this  case you would not need both sender SOAP adapter and a sender agreement.
    /people/stefan.grube/blog/2006/09/21/using-the-soap-inbound-channel-of-the-integration-engine
    Regards
    Bhavesh
    Regards
    Bhavesh

  • ICommand Authentication Error

    Hi there,
    this should be an obvious thing, which is why it's getting so frustrating.  I'm using MII 12.1 SP 5 and want to test the iCommand Display Template with Authentication for a normal SQL insert statement. 
    In the iCommand Display Template, I've selected the following:
    - Audit Checkbox
    - "SAP_XMII_Administrator" for the Command Audit Role 1
    - Command Audit Role 1 Logon Required Checkbox
    - I've entered some text for: "Category", "Command Text" and "Return Message"
    The rest of the configurations have been left blank.
    When I try to run the javascript:
    iCommand.executeCommand();
    I get the java pop up window for the role authentication (username and password entry).  I capture the details of a user which belongs to the SAP_XMII_Administrator role (and all the other SAP_XMII roles too).  I then get the error message:
    "Authentication Check 1: Authentication failed; the query will not run.
    SAP_XMII_Administrator Role is required to authenticate"
    Has anyone come across this problem?
    Thanks

    Hi Kevin,
    thanks.  Had a look at the logs and it throws an error about not being able to find the template.  I won't copy all the details in, but the first bit is the following:
    Severity          Date     Time               Message          Category                      Location                           Application
    Warning     07/05/2010     21:29:47:203     No Template Defined     /Applications/XMII     com.sap.xmii.Illuminator.templates.TemplateManager     sap.com/xapps~xmii~ear
    Error     07/05/2010     21:29:47:375     Catalog Service Error     /Applications/XMII/Xacute     com.sap.xmii.servlet.Catalog     sap.com/xapps~xmii~ear
    Error     07/05/2010     21:29:47:375     Catalog Service Error     com.sap.xmii.servlet.Catalog     com.sap.xmii.servlet.Catalog     sap.com/xapps~xmii~ear
                   [EXCEPTION]               
                   com.sap.xmii.Illuminator.logging.LHException: Template was not found; cannot load Predefined/AuditServiceVerify               
    at com.sap.xmii.common.CatalogUtil.doLoad(CatalogUtil.java:138)
    at com.sap.xmii.servlet.Catalog.handleLoad(Catalog.java:394)
    at com.sap.xmii.servlet.Catalog.service(Catalog.java:140)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:162)
    at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:81)
    at com.sap.xmii.system.SecurityFilter.doFilter(SecurityFilter.java:96)
    at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:73)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:441)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:291)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:396)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:385)
    at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:48)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    And then a few more lines of exceptions which don't seem to be associated with the problem.  Could this mean that the iCommand Template is not being picked up?  It must've found something to know that the SAP_XMII_Administrator Role had to be used.
    Thanks

  • XMII Portal Login Page

    Hi ,
    I am unable to view the login screen for the xMII portal.
    I tried to access the login page from the system where the xmII server is installed.
    When i type in the url -- http://<server>/Lighthammer/Login.jsp it directs me to the menu page without asking my username and password.
    Are there any settings to enable the authentication page??
    Please help.
    Message was edited by:
            vaishali dhayalan

    Hi Shyam,
    The configuration below is the trusted server configuration for the system being used
    Name  --               localhost
    Description --        localhost
    IP  --                    127.0.0.1 (IP address of the system used)
    I am unable to delete this configuration since my delete button is disabled even after selecting the server config.How else could i delete it?
    Will there be a problem if we delete this server config??
    Please help.
    Message was edited by:
            vaishali dhayalan
    Message was edited by:
            vaishali dhayalan

  • XMII 12.0 on NW 7.1 CE?

    I installed the NW 7.1 CE developer preview and installed xMII 12.0 via JSPM.  I created my 3 groups, XMII Administrators, XMII Users, and XMII Developers and assigned them to my user.  I upgraded my JCO DLLs (Windows XP SP-latest).  I restarted NW 7.1 CE.  When I go to URL http://myhost:50100/XMII (or .../XMII/Menu.jsp), I get the following stack dump:
    Details: com.sap.engine.services.jmsconnector.exceptions.BaseDeploymentException: Class loading error: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Error getting the server-side naming service functionality during getInitialContext operation.
         at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:251)
         at com.sap.engine.system.naming.provider.DefaultInitialContext._getDefaultInitCtxt(DefaultInitialContext.java:64)
         at com.sap.engine.system.naming.provider.DefaultInitialContext.<init>(DefaultInitialContext.java:45)
         at com.sap.engine.system.naming.provider.DefaultInitialContextFactory.getInitialContext(DefaultInitialContextFactory.java:41)
         at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
         at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)
         at javax.naming.InitialContext.init(InitialContext.java:223)
         at javax.naming.InitialContext.<init>(InitialContext.java:197)
         at com.sap.engine.services.jmsconnector.container.JmsContainerImpl.loadFactory(JmsContainerImpl.java:1325)
         at com.sap.engine.services.jmsconnector.container.JmsContainerImpl.prepareStart(JmsContainerImpl.java:585)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:211)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:171)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:393)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:480)
         at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:537)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:230)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:374)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:2955)
         at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:736)
         at com.sap.engine.services.servlets_jsp.server.deploy.impl.ApplicationManager.start(ApplicationManager.java:175)
         at com.sap.engine.services.servlets_jsp.server.deploy.impl.ApplicationManager.analyseAppStatusMode(ApplicationManager.java:279)
         at com.sap.engine.services.servlets_jsp.server.DeployContext.startLazyApplication(DeployContext.java:334)
         at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:86)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
         at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:67)
         at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
         at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
         at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
         at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
         at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
         at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
         at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
         at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:308)
         at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.run(Processor.java:221)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:137)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:229)
    Caused by: com.sap.engine.services.jndi.persistent.exceptions.NoPermissionException: Exception during getInitialContext operation. Wrong security principle/credentials. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Cannot authenticate the user.]
         at com.sap.engine.services.jndi.implclient.LoginHelper.serverSideLogin(LoginHelper.java:70)
         at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:143)
         ... 41 more
    Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Cannot authenticate the user.
         at com.sap.engine.services.security.login.ModulesProcessAction.run(ModulesProcessAction.java:177)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.services.security.login.FastLoginContext.login(FastLoginContext.java:217)
         at com.sap.engine.services.jndi.implclient.LoginHelper.serverSideLogin(LoginHelper.java:60)
         ... 42 more
    Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Authentication did not succeed.
         at com.sap.engine.services.security.server.jaas.BasicPasswordLoginModule.login(BasicPasswordLoginModule.java:149)
         at com.sap.engine.services.security.login.LoginModuleLoggingWrapperImpl.login(LoginModuleLoggingWrapperImpl.java:189)
         at com.sap.engine.services.security.login.ModulesProcessAction.run(ModulesProcessAction.java:71)
         ... 45 more
    com.sap.engine.services.jndi.persistent.exceptions.NamingException: Error getting the server-side naming service functionality during getInitialContext operation.
         at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:251)
         at com.sap.engine.system.naming.provider.DefaultInitialContext._getDefaultInitCtxt(DefaultInitialContext.java:64)
         at com.sap.engine.system.naming.provider.DefaultInitialContext.<init>(DefaultInitialContext.java:45)
         at com.sap.engine.system.naming.provider.DefaultInitialContextFactory.getInitialContext(DefaultInitialContextFactory.java:41)
         at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
         at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)
         at javax.naming.InitialContext.init(InitialContext.java:223)
         at javax.naming.InitialContext.<init>(InitialContext.java:197)
         at com.sap.engine.services.jmsconnector.container.JmsContainerImpl.loadFactory(JmsContainerImpl.java:1325)
         at com.sap.engine.services.jmsconnector.container.JmsContainerImpl.prepareStart(JmsContainerImpl.java:585)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:211)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:171)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:393)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:480)
         at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:537)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:230)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:374)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:2955)
         at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:736)
         at com.sap.engine.services.servlets_jsp.server.deploy.impl.ApplicationManager.start(ApplicationManager.java:175)
         at com.sap.engine.services.servlets_jsp.server.deploy.impl.ApplicationManager.analyseAppStatusMode(ApplicationManager.java:279)
         at com.sap.engine.services.servlets_jsp.server.DeployContext.startLazyApplication(DeployContext.java:334)
         at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:86)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
         at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:67)
         at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
         at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
         at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
         at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
         at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
         at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
         at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
         at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:308)
         at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.run(Processor.java:221)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:137)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:229)
    Caused by: com.sap.engine.services.jndi.persistent.exceptions.NoPermissionException: Exception during getInitialContext operation. Wrong security principle/credentials. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Cannot authenticate the user.]
         at com.sap.engine.services.jndi.implclient.LoginHelper.serverSideLogin(LoginHelper.java:70)
         at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:143)
         ... 41 more
    Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Cannot authenticate the user.
         at com.sap.engine.services.security.login.ModulesProcessAction.run(ModulesProcessAction.java:177)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.services.security.login.FastLoginContext.login(FastLoginContext.java:217)
         at com.sap.engine.services.jndi.implclient.LoginHelper.serverSideLogin(LoginHelper.java:60)
         ... 42 more
    Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Authentication did not succeed.
         at com.sap.engine.services.security.server.jaas.BasicPasswordLoginModule.login(BasicPasswordLoginModule.java:149)
         at com.sap.engine.services.security.login.LoginModuleLoggingWrapperImpl.login(LoginModuleLoggingWrapperImpl.java:189)
         at com.sap.engine.services.security.login.ModulesProcessAction.run(ModulesProcessAction.java:71)
         ... 45 more
         at com.sap.engine.services.jmsconnector.container.JmsContainerImpl.loadFactory(JmsContainerImpl.java:1339)
         at com.sap.engine.services.jmsconnector.container.JmsContainerImpl.prepareStart(JmsContainerImpl.java:585)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:211)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:171)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:393)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:480)
         at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:537)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:230)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:374)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:2955)
         at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:736)
         at com.sap.engine.services.servlets_jsp.server.deploy.impl.ApplicationManager.start(ApplicationManager.java:175)
         at com.sap.engine.services.servlets_jsp.server.deploy.impl.ApplicationManager.analyseAppStatusMode(ApplicationManager.java:279)
         at com.sap.engine.services.servlets_jsp.server.DeployContext.startLazyApplication(DeployContext.java:334)
         at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:86)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
         at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:67)
         at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
         at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
         at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
         at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
         at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
         at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
         at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
         at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:308)
         at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.run(Processor.java:221)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:137)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:229)
    Any ideas?
    -tim

    Here's more detail on the JCO error I'm getting in case anyone has a suggestion:
    An error occurred trying to start server DMO210-TIM
    [EXCEPTION]
    com.sap.mw.jco.JCO$Exception: (102) JCO_ERROR_COMMUNICATION: A pool with the identifier 'DMO210-TIM' already exists
    at com.sap.mw.jco.JCO$PoolManager.addPool(JCO.java:6072)
    at com.sap.mw.jco.JCO.addClientPool(JCO.java:8402)
    at com.sap.xmii.databuffer.util.JCoServerManager.startServer(JCoServerManager.java:302)
    at com.sap.xmii.Illuminator.gui.handlers.JCoServerHandler.processConfiguration(JCoServerHandler.java:249)
    at com.sap.xmii.Illuminator.gui.handlers.JCoServerHandler.process(JCoServerHandler.java:123)
    at com.sap.xmii.servlet.Admin.service(Admin.java:65)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:163)
    at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:82)
    at com.sap.xmii.system.SecurityFilter.doFilter(SecurityFilter.java:97)
    at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:74)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:425)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:288)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:376)
    at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:85)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
    at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:160)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
    at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:67)
    at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
    at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
    at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
    at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
    at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
    at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:308)
    at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.run(Processor.java:221)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:137)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:229)
    Date: 2007-10-04
    Time: 18:32:22:953
    Category: com.sap.xmii.Illuminator.gui.handlers.JCoServerHandler
    Location: com.sap.xmii.Illuminator.gui.handlers.JCoServerHandler
    Application: sap.com/XMIIEnterpriseApplication
    Thread: HTTP Worker [4]
    Data Source: j2ee\cluster\server0\log\defaultTrace_00.trc
    Message ID: 190632500000048277
    Argument Objects: 
    Arguments: 
    DSR Component: 
    DSR Transaction: acedc99072c911dcca9d0015c55394ba
    DSR User: 
    Message Code: 
    Session: 40
    Transaction: 
    User: Administrator
    Host: Timdruryxp
    System: TD1
    Instance: J01
    Node: server0

  • Xmii login password restrictions

    Hi,
    We want to make xMII login password more secure by putting length restriction, special characters etc.
    We are using xMII 11.5.3 b66, please advise how to put password restriction if it is possible with this xMII version.
    Thanks and Regards,
    Alok

    You would need to use another mechanism to provide your authentication, such as LDAP, which can be configured in LHSecurity.
    Regards,
    Jamie

  • XMII-MES integration

    Hi,
    Has anyone worked on xMII-MES integration...
    I'm exploring ways of connecting different MES softwares with xMII...
    In case any of you have any idea about ways of integrating xMII and MES, plz let me know
    Ur responses are valued...
    Thanks,
    Ajitha
    Message was edited by:
            Ajitha Buvan

    Hello Srinivas,  I would have responded yesterday but for some reason my SDN account was locked and I couldn't log in.
    Our current ERP-to-MES feeds involve sending MATMAS, BOMMAT, LOIROU, LOIPRO, CLFMAS, and a few others.  The ERP is typically configured to send these upon saving their respective business object (material, BOM, routing, etc.) using change pointers, but that's not my expertise.  In some cases, we supplement the data from the IDOCs with RFC calls - e.g. revisions on the material.  We have a few other download feeds being developed now but since I don't yet know what will and won't be included in the next release, I won't mention them.
    We use xMII to take the IDOCs using either the built-in IDOC listener or as a SOAP message to another xMII transaction.  The IDOCs are persisted so if any connectivity or system failures occur, we can retry them later.  Depending on the complexity of the mapping from IDOC to our MES object model, we may use only an XSLT to transform the IDOC or we may use a combination of the xMII BLS and our XSLTs to perform the transformations.  Some data enrichment may take place using the xMII BLS - some is necessary for building some MES required fields that the ERP doesn't provide and others are deployment-specific. 
    The resulting XML is suitable to send to Visiprise Manufacturing - we wrap it with SOAP and call the appropriate VM web service.  Note that VM requires WS-Security which puts authentication credentials in the SOAP header and, as of xMII 11.5 SR02, the xMII Web Service action doesn't support SOAP headers.  We used the HTTP Post action and got creative with HTTP headers to inject the required SOAPAction header.
    For the MES-to-ERP interfaces, we support the typical operation confirmation/scrap BAPI calls.  We also provide manual backflush if desired.  These are implemented by either synchronous or asynchronous web service calls from Visiprise Manufacturing to xMII.  VM uses JMS internally to disassociate the user thread from the confirmation to support asynchronous handling.  These confirmations are collected in xMII and batched according to the manufacturing style: for discrete manufacturing confirmations are batched by order; for repetitive manufacturing they're batched by production version.  The appropriate BAPI is then called and status reported back to VM via a status/event notification web service.
    When discussing these interfaces it easy to lose track of the bigger picture - the actual business scenarios you're trying to solve.  SAP is the system of record of Materials, BOMs, Routings (not all the time!), and Orders.  Visiprise Manufacturing, as the MES, is the system of record of all WIP (work in progress) and As-Built information (exactly what components were assembled into which finished products).  Often the most valuable scenarios are those which require orchestration between both systems to produce an answer to questions like,
    Q: "Where is Customer X's order?"
    A: "3 units are assembled and packed, 1 is at Operation 0090, and 2 have not been started because component 123 is on back-order."
    or,
    Q: "Where is the component with serial number ABC and which customer received it?"
    A: "Component with serial number ABC was assembled onto MES control number 999 on 3/17/2007 at 3:30PM by Joe P.  MES control number 999 was marked with serial number XYZ and completed on 3/20/2007 and moved to warehouse 001 on 3/21/2007.  It was shipped to Customer Z on 3/22/2007, ..."
    and so on...
    The existing IDOCs/BAPIs can answer these questions, but things start getting interesting when you explore SAP's new SOA push - in particular the ES architecture around MES.  In my opinion, it's not all there yet, but I participated in the ES MES community workshop a few weeks ago and was encouraged that SAP was listening to our ideas.  I look forward to the day when Visiprise Manufacturing and SAP web services reside together in the same registry/repository and are orchestrated via BPEL.

  • XMII SSO with Sharepoint

    I am new to xMII platform and would like to know few details on foll:
    SAP ECC users are authenticated on their own LDAP server.
    We are about to create a manufacturing portal using sharepoint that will access iview-webparts from MII platform.
    Sharepoint users will be on ADS.  Now how do i achieve SSO between Sharepoint and MII.
    Do i use credential mappings at Sharepoint side or is there a better way to do ? like SAML, etc

    Ajay,
    LDAP should work for your scenario. Sharepoint Active Directory can also use LDAP.
    I assume you are talking about SharePoint 2007. If so, it does support LDAP authentication by using the LDAP membership provider. Have a look on the link
    http://technet.microsoft.com/en-us/library/cc262069.aspx
    Below link can provide in detail information about the SSO on SAP landscape.
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/47d0cd90-0201-0010-4c86-f81b1c812e50
    http://help.sap.com/saphelp_nw70/helpdata/EN/12/9f244183bb8639e10000000a1550b0/frameset.htm
    Thanks
    Ram Upadhyay

  • 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>

  • Authentication - multiple domains with multiple accounts

    Dear All,
    Consider an environment where a user, Joe Bloggs, has an account on two Windows domains:  DOMA and DOMB.  DOMA is a domain that all users in the organisation are members of.  DOMB is a domain used by a smaller subset of users.  The user's
    machine is part of the DOMB domain.
    I'd like to deploy SharePoint 2013 on DOMA and have the user, logged on to their DOMB machine, seamlessly authenticate (through IWA) with SharePoint 2013.  
    So far, I've thought of the following solutions:
    1.  Build a trust between the two domains.  Possible, but the AD information in DOMA is more up-to-date than that in DOMB and I'd like to use that to populate SharePoint user profiles.  Also, DOMB is likely to be deprecated in the future.
    2.  Use WorkPlace Join.  Unfortunately, devices are running Windows 7 and WorkPlace Join only works for devices running Windows 8.
    I've wondered whether it's possible to map two accounts on separate domains together so that a user on DOMB can effectively masquerade as their corresponding user on DOMA when authenticating with SharePoint, but haven't come across a way of doing this, yet.
    Any ideas?  Or, am I completely mad?!
    Thanks in advance.

    1) Is your only option for seamless logon with IWA. It is not possible to map accounts "together" so-to-speak. SharePoint stores a reference to the user's SID, which must match the user making the request.
    An ADFS trust might be another option, although that increases your deployment footprint and complexity.
    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.

  • Error while authenticating a user

    Dear all,
    Hope you all are doing well.
    Production issue :
    When an user tries to login with his username and password. He is getting error message "INTERNAL ERROR OCCURED".
    And the standard RFC which i'm using for authenticating user is  SUSR_LOGIN_CHECK_RFC
    CALL FUNCTION 'SUSR_LOGIN_CHECK_RFC'
      EXPORTING
           bname                                 = ip_empid
           password                             = ip_password
    EXCEPTIONS
           wait                                     = 1
           user_locked                          = 2
           user_not_active                    = 3
           password_expired                 = 4
           wrong_password                   = 5
           no_check_for_this_user         = 6
           password_attempts_limited    = 7
           internal_error                         = 8
    OTHERS                                    = 9.
    I want to know what is the meaning of this internal error ? something is going wrong with the standard RFC which I am referring to ? Some one please help me out..
    Thanks in advance.

    Hi Syed,
    Really need more of a context to your problem.
    1. You've posted in the SSO forum. A SSO problem or a normal SAPGUI logon problem ?
    2. You say .... "And the standard RFC which i'm using for authenticating user is  SUSR_LOGIN_CHECK_RFC" .... Meaning what ??? you are using a home developed solution ?
    3. Problem affects one user or all users ?
    4. Backend version and kernel pl level please.
    Cheers,
    Amerjit

  • Authenticating test applcation in OAM is not working

    Hello OAM experts, can you please help to figure out why my test application is not getting authenticated by OAM.
    I have installed IDM for fusion application and SSO login is working for all admin consoles such as WLS, EM, OAM, OIM. I have deployed test application to OAM server itself to test the authentication of protected resources.
    Host identifier is already there which was create while configuring my IDM for fusion applications. I created new application domain , created resource for /text/*, created authentication policy and used LDAPScheme for authentication, created authorization policy and defined constraints by adding a group OAMAdministrators ( just for testing purpose). I also added response in the authentication policy.
    Then I have configured admin.conf of OHS server to redirect http://webhost1:7777/test to oam server host and port. It is getting redicted but not to the SSO login page. The URL still shows http://webhost1:7777/test and executes the test page and displays test application. It should have been redirected to SSO login page though OAM.
    At this stage I have no clue what did I miss. As I said, when I login to wls console, it gets redicted to SSO login through OAM login page and then while accessing OIM, it directly takes me to OIM application since the user has privileges and also OAM page without logging in again.
    But why my test application is not redirected to OAM authentication page ?
    Any help is grately appreciated.
    thanks
    Edited by: Jyothi on May 3, 2012 3:25 AM

    Hi, I am having the same issue. I am new to all this OAM stuff. I am using OAM 11g with a 11g Webgate configured. When I try to access the OAM Console the SSO setup does work and kicks-in and redirects me to the OAM server's integrated login page. But my test application that lives on an app server installed on a separate machine is never challenged for their credentials. As the documentation says I have CLIENT-CERT defined as the auth-method in my login-config inside my applications web.xml file.
    I think I am not using the right providers. What I want is Identity Assertion and also OAM authentication (if Identity Assertion fails Authentication should kick-in and redirect to challenge login page). So I have an OAMIdentityAsserter and an OAMAUthenticator set-up in addition to the Default Weblogic Identity Asserter and Default Weblogic Authenticator.
    I have tried everything but, the login redirect never happens. If I use the DefaultAuthenticator along with OAMAuthenticator (no OAMIdentityAsserter) and define BASIC in my login-config in web.xml then the Default Weblogic Authenticator pops up a dialog box which does let me enter credentials and when I do it does make the trip to the OAM server and works flawlessly. But I don't want basic authentication and I don't want a dialogue box to pop-up. I want the OAM server to redirect me to it's built-in login page just like it does for the OAMConsole itself which is being protected by the out of the box 10g IAMSuiteAgent Webgate. Which, as you know, comes pre-installed.
    Please let me know your configuration and the providers you have set up and how you were able to make the OAM server challenge you for credentials when trying to access a protected resource/application.
    Thank You.

Maybe you are looking for