Restrict multi login in Portal

Hi,
I want to restrict multi login in Portal.
I have java + abap dual stack.
Please give me the solution.
"award point waiting..for  solution......"

I don't want to restrict multiple person.
I want to provide single session for each user.
More than single session will terminate , when the same user login for second session.
I think, now u understand my issue.

Similar Messages

  • How to install multi language in Portal?

    Hi,
    Can someone give me the directions in how to install multi
    language in Portal? I found the "langinst.cmd" file under
    ORACLE_HOME\portal30\admin\plsql, also another
    file "langinst.sql" under ORACLE_HOME\portal30
    \admin\plsql\nlsres.
    I am not quite sure how I can do that, which file I should use.
    And once I installed the multi language, can I just go into
    portal to create a new content area and using the multi language?
    Thanks for any comment in advance!
    Kelly.

    Hi Kelly
    You need to identify parameters for this file and run file. Its
    langinst.cmd for WINNT and langinst.csh for UNIX.
    1.     From the dos prompt , go to the following directory on
    your server.
         Oracle/iSuites/portal30/admin/plsql/
    2.     Set the Oracle_Home to = oracle/iSuites/
    3.     Run the command
    langinst.csh -s portal30 -p portal30 -o
    PORTAL30_SSO -d PORTAL30_SSO -c oid -l ar -available
    s - schema
    p - password
    o - < login server - in your case it may be portal30_SSO >
    d - <password- maybe portal30_sso>
    c - connect string
    l - language (which is set to ar )
    ar is arabic which i ve set
    Good Luck
    Regards
    Yogesh

  • Unable to login to portal and any links in index.html page

    Hi,
    I am not able to login to portal. Only able to login to System information link.
    Whenever I try to login to other links, I have been taken to User input screen. After I enter the username and password, I am getting response as if Page is refreshed.
    Only log geting updated is default trace during this action.
    Few Error messages from default trace file during this action:
    #1.5 #00188B34FD3300590000002E000065BC0004620157F23D55#1233657817007#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#sap.com/tcwddispwda#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#J2EE_GUEST#0##n/a##8310f2f3f1df11dda01a00188b34fd33#SAPEngine_Application_Thread[impl:3]_11##0#0#Error#1#/System/Server/WebRequests#Plain###application [webdynpro/dispatcher] Cannot send an HTTP error response [500 Application error occurred during request processing. (details: java.lang.NullPointerException: null)].
    The error is: com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException: An attempt to write after the stream had been closed.
    Exception id: [00188B34FD3300590000002C000065BC0004620157F23ADA]#
    #1.5 #00188B34FD33006500000035000065BC00046201585A3EDE#1233657823820#com.sap.engine.services.security.authentication.logonapplication#sap.com/com.sap.security.core.admin#com.sap.engine.services.security.authentication.logonapplication.doLogon#J2EE_GUEST#0##n/a##8722f8c0f1df11dd933700188b34fd33#SAPEngine_Application_Thread[impl:3]_4##0#0#Error##Java###doLogon failed
    [EXCEPTION]
    #1#com.sap.security.core.logon.imp.UMELoginException
         at com.sap.security.core.logon.imp.SAPJ2EEAuthenticator.logon(SAPJ2EEAuthenticator.java:949)
         at com.sap.security.core.logonadmin.ServletAccessToLogic.logon(ServletAccessToLogic.java:208)
         at com.sap.security.core.sapmimp.logon.SAPMLogonLogic.doLogon(SAPMLogonLogic.java:914)
         at com.sap.security.core.sapmimp.logon.SAPMLogonLogic.uidPasswordLogon(SAPMLogonLogic.java:578)
         at com.sap.security.core.sapmimp.logon.SAPMLogonLogic.executeRequest(SAPMLogonLogic.java:158)
         at com.sap.security.core.sapmimp.logon.SAPMLogonServlet.doPost(SAPMLogonServlet.java:60)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    Regards,
    Nallasivam.D

    Hi,
    have already read this thread:
    it´s nearly the same problem.
    Have you checked if the java guest account is enabled? Please check note 1231650.
    Best Regards,
    Jens

  • Able to login into Portal with http but not https

    NT4
    8.1.6.3 DB
    9iAS 1.0.2.2
    Oracle Portal 3.0.9
    I have been following Note 136153.1 to configure Oracle Portal to use HTTPS.
    I am able to login into Portal using http(e.g) http://machinename.net/pls/portal30. I have configured http.conf asdescribed in
    136153 and used the ssodatan script to associate the login server with https.
    I am able to connect to https://machinename.net and can see theSecurity
    Certificate. I am also to login into
    https://machinename.net/pls/portal30/admin_/gateway.htm?schema=portal30 and see
    the Gateway configuration. It is only when I go to
    https://machinename.net/pls/portal30 I receive the error message -
    Error: Timeout
    occurred whilst retrieving page meta data.
    If I revert the settings back toPort 80 in http.conf back to Port 80 and
    re-run ssodatan using http://machinename.net/pls/portal30 etc then I am able to
    succesfully log intoPortal
    Can anyone help with this?
    null

    Hi Arun,
    Most of the times unable to login to portal causes due to network problems
    Please ensure in backend system all application servers are up in SM51
    if it is happening every day same time check java patches

  • "In the Data Palette window, drag the Login to Portal portlet ..."?

    Hi;
    In http://e-docs.bea.com/workshop/docs81/doc/en/portal/samples/login.html?skipReload=true it says "In the Data Palette window, drag the Login to Portal portlet onto a placeholder on the page. "What does this mean and how do I do it?
    And the following line is "In the Property Editor window, set any relevant properties." - where is the property window and what properties do I want to set and to what value?
    thanks - dave

    Help please
    thanks - dave

  • Full Qualified Domain Name (FQDN) doesn't work when try to login in portal

    I Install a NetWeaver 7.0 with BI JAVA
    SP15
    I try to login in portal with 3 diferent ways:
    1) - With IP I can login but I can't see any objects;
    2) - With only hostname without domain I can login I see objects, every thing works fine.
    3) - With FQDN I can't login. I don't get any error. It refreh again the login page, and ask again the user and pass.
    I could always login with only the hostname, but the problem is that all links are generated with FQDN.
    This is the error that is in Security.log:
    #1.5 #0050568F3C72005B0000026A00000B000004555928D4E3E7#1219741332358#/System/Security/Audit#sap.com/irj#com.sap.security.core.util.SecurityAudit#SAP_BASIS#5575##slmqlsbi1.lm.pt_BIP_3925050#Guest#abd12770734d11dd889a0050568f3c72#SAPEngine_Application_Thread[impl:3]_4##0#0#Info#1#com.sap.security.core.util.SecurityAudit#Plain###SAP_BASIS     | LOGIN.OK     | USER.R3_DATASOURCE.SAP_BASIS     |      | IP Address=[192.168.4.4]#
    #1.5 #0050568F3C72005F000014BF00000B000004555928F31063#1219741334343#/System/Security/Audit/J2EE#sap.com/irj#com.sap.engine.services.security.roles.SecurityRoleImpl#J2EE_GUEST#5576##n/a##28fb55a072da11dd9b760050568f3c72#Thread[Thread-50,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Info#1#com.sap.engine.services.security.roles.SecurityRoleImpl#Java###: Authorization check for caller assignment to J2EE security role [ : ].#3#ACCESS.OK#SAP-J2EE-Engine#guests#
    #1.5 #0050568F3C720075000005CA00000B00000455592934EDEE#1219741338656#/System/Security/Authentication#sap.com/irj#com.sap.engine.services.security.authentication.logincontext#SAP_BASIS#5577##slmqlsbi1.lm.pt_BIP_3925050#Guest#af8afb20734d11ddc4230050568f3c72#SAPEngine_Application_Thread[impl:3]_33##0#0#Info#1#com.sap.engine.services.security.authentication.logincontext#Plain###LOGIN.OK
    User: SAP_BASIS
    Authentication Stack: ticket
    Login Module                                                               Flag        Initialize  Login      Commit     Abort      Details
    1. com.sap.security.core.server.jaas.EvaluateTicketLoginModule             SUFFICIENT  ok          false      false                
    2. com.sap.engine.services.security.server.jaas.BasicPasswordLoginModule   REQUISITE   ok          true       true                 
    3. com.sap.security.core.server.jaas.CreateTicketLoginModule               OPTIONAL    ok          true       true                 
    Central Checks                                                                                true                  #
    #1.5 #0050568F3C720075000005CB00000B00000455592934F1FE#1219741338656#/System/Security/Audit#sap.com/irj#com.sap.security.core.util.SecurityAudit#SAP_BASIS#5577##slmqlsbi1.lm.pt_BIP_3925050#Guest#af8afb20734d11ddc4230050568f3c72#SAPEngine_Application_Thread[impl:3]_33##0#0#Info#1#com.sap.security.core.util.SecurityAudit#Plain###SAP_BASIS     | LOGIN.OK     | USER.R3_DATASOURCE.SAP_BASIS     |      | IP Address=[192.168.4.4]#
    #1.5 #0050568F3C72005F000014C000000B0000045559298BC213#1219741344346#/System/Security/Audit/J2EE#sap.com/irj#com.sap.engine.services.security.roles.SecurityRoleImpl#J2EE_GUEST#5578##n/a##28fb55a072da11dd9b760050568f3c72#Thread[Thread-50,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Info#1#com.sap.engine.services.security.roles.SecurityRoleImpl#Java###: Authorization check for caller assignment to J2EE security role [ : ].#3#ACCESS.OK#SAP-J2EE-Engine#guests#
    #1.5 #0050568F3C72005F000014C100000B00000455592A2466F9#1219741354348#/System/Security/Audit/J2EE#sap.com/irj#com.sap.engine.services.security.roles.SecurityRoleImpl#J2EE_GUEST#5579##n/a##28fb55a072da11dd9b760050568f3c72#Thread[Thread-50,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Info#1#com.sap.engine.services.security.roles.SecurityRoleImpl#Java###: Authorization check for caller assignment to J2EE security role [ : ].#3#ACCESS.OK#SAP-J2EE-Engine#guests#
    Can you tell me why I can't login in portal with FQDN?
    Best regards,
    Filipe Sacadura Botte
    Edited by: Filipe Sacadura Botte on Aug 26, 2008 11:03 AM

    I have all that configured:
    File host:
    IP host FQDN
    File Security.log
    #1.5 #0050568F3C72006D000002C700000E580004556D63F80A15#1219828223462#/System/Security/Audit#sap.com/irj#com.sap.security.core.util.SecurityAudit#J2EE_ADMIN#7764##slmqlsbi1_BIP_3925050#Guest#fae2cba0741711dd91c40050568f3c72#SAPEngine_Application_Thread[impl:3]_1##0#0#Info#1#com.sap.security.core.util.SecurityAudit#Plain###J2EE_ADMIN     | LOGIN.OK     | USER.R3_DATASOURCE.J2EE_ADMIN     |      | IP Address=[10.131.224.205]#
    #1.5 #0050568F3C72006300001DB400000E580004556D64287F5C#1219828226635#/System/Security/Audit/J2EE#sap.com/irj#com.sap.engine.services.security.roles.SecurityRoleImpl#J2EE_GUEST#7765##n/a##e398c660736e11dda4c50050568f3c72#Thread[Thread-50,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Info#1#com.sap.engine.services.security.roles.SecurityRoleImpl#Java###: Authorization check for caller assignment to J2EE security role [ : ].#3#ACCESS.OK#SAP-J2EE-Engine#guests#
    #1.5 #0050568F3C72006300001DB500000E580004556D64C1226C#1219828236635#/System/Security/Audit/J2EE#sap.com/irj#com.sap.engine.services.security.roles.SecurityRoleImpl#J2EE_GUEST#7766##n/a##e398c660736e11dda4c50050568f3c72#Thread[Thread-50,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Info#1#com.sap.engine.services.security.roles.SecurityRoleImpl#Java###: Authorization check for caller assignment to J2EE security role [ : ].#3#ACCESS.OK#SAP-J2EE-Engine#guests#
    #1.5 #0050568F3C720076000000E400000E580004556D64CDE4A3#1219828237479#/System/Security/Authentication#sap.com/irj#com.sap.engine.services.security.authentication.logincontext#J2EE_ADMIN#7767##slmqlsbi1_BIP_3925050#Guest#034bcf80741811dd8c500050568f3c72#SAPEngine_Application_Thread[impl:3]_36##0#0#Info#1#com.sap.engine.services.security.authentication.logincontext#Plain###LOGIN.OK
    User: J2EE_ADMIN
    Authentication Stack: ticket
    Login Module                                                               Flag        Initialize  Login      Commit     Abort      Details
    1. com.sap.security.core.server.jaas.EvaluateTicketLoginModule             SUFFICIENT  ok          false      false                
    2. com.sap.engine.services.security.server.jaas.BasicPasswordLoginModule   REQUISITE   ok          true       true                 
    3. com.sap.security.core.server.jaas.CreateTicketLoginModule               OPTIONAL    ok          true       true                 
    Central Checks                                                                                true                  #
    #1.5 #0050568F3C720076000000E500000E580004556D64CDE766#1219828237479#/System/Security/Audit#sap.com/irj#com.sap.security.core.util.SecurityAudit#J2EE_ADMIN#7767##slmqlsbi1_BIP_3925050#Guest#034bcf80741811dd8c500050568f3c72#SAPEngine_Application_Thread[impl:3]_36##0#0#Info#1#com.sap.security.core.util.SecurityAudit#Plain###J2EE_ADMIN     | LOGIN.OK     | USER.R3_DATASOURCE.J2EE_ADMIN     |      | IP Address=[10.131.227.30]#
    #1.5 #0050568F3C720078000000D100000E580004556D653EF26F#1219828244886#/System/Security/Authentication#sap.com/irj#com.sap.engine.services.security.authentication.logincontext#J2EE_ADMIN#7768##slmqlsbi1_BIP_3925050#Guest#07b14c80741811dd94540050568f3c72#SAPEngine_Application_Thread[impl:3]_18##0#0#Info#1#com.sap.engine.services.security.authentication.logincontext#Plain###LOGIN.OK
    User: J2EE_ADMIN
    Authentication Stack: ticket
    Login Module                                                               Flag        Initialize  Login      Commit     Abort      Details
    1. com.sap.security.core.server.jaas.EvaluateTicketLoginModule             SUFFICIENT  ok          false      false                
    2. com.sap.engine.services.security.server.jaas.BasicPasswordLoginModule   REQUISITE   ok          true       true                 
    3. com.sap.security.core.server.jaas.CreateTicketLoginModule               OPTIONAL    ok          true       true                 
    Central Checks                                                                                true                  #
    #1.5 #0050568F3C720078000000D200000E580004556D653EF5CD#1219828244886#/System/Security/Audit#sap.com/irj#com.sap.security.core.util.SecurityAudit#J2EE_ADMIN#7768##slmqlsbi1_BIP_3925050#Guest#07b14c80741811dd94540050568f3c72#SAPEngine_Application_Thread[impl:3]_18##0#0#Info#1#com.sap.security.core.util.SecurityAudit#Plain###J2EE_ADMIN     | LOGIN.OK     | USER.R3_DATASOURCE.J2EE_ADMIN     |      | IP Address=[10.131.227.30]#
    #1.5 #0050568F3C72006300001DB600000E580004556D6559DF5B#1219828246652#/System/Security/Audit/J2EE#sap.com/irj#com.sap.engine.services.security.roles.SecurityRoleImpl#J2EE_GUEST#7769##n/a##e398c660736e11dda4c50050568f3c72#Thread[Thread-50,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Info#1#com.sap.engine.services.security.roles.SecurityRoleImpl#Java###: Authorization check for caller assignment to J2EE security role [ : ].#3#ACCESS.OK#SAP-J2EE-Engine#guests#
    #1.5 #0050568F3C72007A0000016C00000E580004556D659A15BF#1219828250856#/System/Security/Authentication#sap.com/irj#com.sap.engine.services.security.authentication.logincontext#J2EE_ADMIN#7770##slmqlsbi1_BIP_3925050#Guest#0b36a2b0741811dd8eeb0050568f3c72#SAPEngine_Application_Thread[impl:3]_22##0#0#Info#1#com.sap.engine.services.security.authentication.logincontext#Plain###LOGIN.OK
    User: J2EE_ADMIN
    Authentication Stack: ticket
    Login Module                                                               Flag        Initialize  Login      Commit     Abort      Details
    1. com.sap.security.core.server.jaas.EvaluateTicketLoginModule             SUFFICIENT  ok          false      false                
    2. com.sap.engine.services.security.server.jaas.BasicPasswordLoginModule   REQUISITE   ok          true       true                 
    3. com.sap.security.core.server.jaas.CreateTicketLoginModule               OPTIONAL    ok          true       true                 
    Central Checks                                                                                true                  #
    #1.5 #0050568F3C72007A0000016D00000E580004556D659A18AF#1219828250856#/System/Security/Audit#sap.com/irj#com.sap.security.core.util.SecurityAudit#J2EE_ADMIN#7770##slmqlsbi1_BIP_3925050#Guest#0b36a2b0741811dd8eeb0050568f3c72#SAPEngine_Application_Thread[impl:3]_22##0#0#Info#1#com.sap.security.core.util.SecurityAudit#Plain###J2EE_ADMIN     | LOGIN.OK     | USER.R3_DATASOURCE.J2EE_ADMIN     |      | IP Address=[10.131.227.30]#
    #1.5 #0050568F3C72006300001DB700000E580004556D65F28856#1219828256653#/System/Security/Audit/J2EE#sap.com/irj#com.sap.engine.services.security.roles.SecurityRoleImpl#J2EE_GUEST#7771##n/a##e398c660736e11dda4c50050568f3c72#Thread[Thread-50,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Info#1#com.sap.engine.services.security.roles.SecurityRoleImpl#Java###: Authorization check for caller assignment to J2EE security role [ : ].#3#ACCESS.OK#SAP-J2EE-Engine#guests#
    #1.5 #0050568F3C72006300001DB800000E580004556D668B39B0#1219828266654#/System/Security/Audit/J2EE#sap.com/irj#com.sap.engine.services.security.roles.SecurityRoleImpl#J2EE_GUEST#7772##n/a##e398c660736e11dda4c50050568f3c72#Thread[Thread-50,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Info#1#com.sap.engine.services.security.roles.SecurityRoleImpl#Java###: Authorization check for caller assignment to J2EE security role [ : ].#3#ACCESS.OK#SAP-J2EE-Engine#guests#
    #1.5 #0050568F3C72006300001DB900000E580004556D6723CECE#1219828276655#/System/Security/Audit/J2EE#sap.com/irj#com.sap.engine.services.security.roles.SecurityRoleImpl#J2EE_GUEST#7773##n/a##e398c660736e11dda4c50050568f3c72#Thread[Thread-50,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Info#1#com.sap.engine.services.security.roles.SecurityRoleImpl#Java###: Authorization check for caller assignment to J2EE security role [ : ].#3#ACCESS.OK#SAP-J2EE-Engine#guests#
    #1.5 #0050568F3C72006300001DBA00000E580004556D67BC791B#1219828286656#/System/Security/Audit/J2EE#sap.com/irj#com.sap.engine.services.security.roles.SecurityRoleImpl#J2EE_GUEST#7774##n/a##e398c660736e11dda4c50050568f3c72#Thread[Thread-50,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Info#1#com.sap.engine.services.security.roles.SecurityRoleImpl#Java###: Authorization check for caller assignment to J2EE security role [ : ].#3#ACCESS.OK#SAP-J2EE-Engine#guests#
    #1.5 #0050568F3C72006300001DBB00000E580004556D685513CD#1219828296657#/System/Security/Audit/J2EE#sap.com/irj#com.sap.engine.services.security.roles.SecurityRoleImpl#J2EE_GUEST#7775##n/a##e398c660736e11dda4c50050568f3c72#Thread[Thread-50,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Info#1#com.sap.engine.services.security.roles.SecurityRoleImpl#Java###: Authorization check for caller assignment to J2EE security role [ : ].#3#ACCESS.OK#SAP-J2EE-Engine#guests#
    #1.5 #0050568F3C72006300001DBC00000E580004556D68EDBF58#1219828306673#/System/Security/Audit/J2EE#sap.com/irj#com.sap.engine.services.security.roles.SecurityRoleImpl#J2EE_GUEST#7776##n/a##e398c660736e11dda4c50050568f3c72#Thread[Thread-50,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Info#1#com.sap.engine.services.security.roles.SecurityRoleImpl#Java###: Authorization check for caller assignment to J2EE security role [ : ].#3#ACCESS.OK#SAP-J2EE-Engine#guests#
    #1.5 #0050568F3C72006300001DBD00000E580004556D69865801#1219828316674#/System/Security/Audit/J2EE#sap.com/irj#com.sap.engine.services.security.roles.SecurityRoleImpl#J2EE_GUEST#7777##n/a##e398c660736e11dda4c50050568f3c72#Thread[Thread-50,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Info#1#com.sap.engine.services.security.roles.SecurityRoleImpl#Java###: Authorization check for caller assignment to J2EE security role [ : ].#3#ACCESS.OK#SAP-J2EE-Engine#guests#
    files std_server0.out and defaultTrace don't have any error.

  • Users created in ABAP tool cannot login to Portal

    Hello,
    I have created a user in abap and assigned them the role SAP_J2EE_ADMIN but cannot login into Portal (Message: User authentication failed) with that user. If I login to portal as J2EE_ADMIN and search for that user I get "No element found." Is there something that needs to be done to get users into Portal? Does authentication not occur against the abap system? Also is the J2EE_ADMIN user only valid within portal and not the abap backend?
    I am using EP7.
    Thanks for any help.

    Hi Kelly,
    I changed it under System Administration>>System Configuration>>UME Configuration>>ABAP System tab. If you read ealier in this thread however, I could not restart the j2ee server after that....so change it at your own risk!
    If you do change it and cannot restart,  go into the config tool and navigate to Global server configuration >> services >> com.sap.security.core.ume.service and find the ume.r3.connection.master.client key. Change that back to it's original value. I was able to restart after that.
    Hope that helps.

  • Multi logins in Oracle application 11i

    Hi All,
    Please any one can tell me that One user can do multiple logins in oracle application with out any issues please explain me..
    And i tried the one user can do multiple logins at the same time and he/she can work but please tell it is effect to any performance issues..
    please give me clarification about multiple logins for one username at the same time for Oracle applications.
    Thanks in Advance...

    One of my user shared his login id, password to some other ppl they are working at the same in different systems i wondered whil one user login id access to multiple logins so i raised this quoitn ..
    if any problem with this multiple lo-gin please tell me..
    and that user had 2 or more responsibilities..
    and please tell me can we restrict login for one user can login one time and can we restrict multiple logins oracle apps 11i.It is possible -- Please see these docs.
    How Can I Restrict Applications Users To Be Signed In Only Once At Any Time [ID 375403.1]
    About the oracle.apps.icx.security.session.created business event. [ID 304209.1]
    R12: Using IE8 to access two EBS Instances runs in error "Unable To Authenticate Session" [ID 1098563.1]
    Thanks,
    Hussein

  • Restricting user login

    This is regarding, restricting user login.
    my application pointing to Oracle Database.
    for example: one user loggedin with userid: nbiaadmin.
    when the same user trying to login using another browser or another system. Then i want to invalidate the existing user's session and allow new user to login.
    how to achieve this?
    please let me know.
    Thanks,
    Natesh.

    You try running maxl with something like
    alter system logout session on application appname force;
    alter application appname disable connects;
    then your load then
    alter application appname enable connects;
    Cheers
    John
    http://john-goodwin.blogspot.com/

  • After the login, the portal displays again the login page

    Hi,
    After Portal Installation the login doesn´t work. The following occurs:
    After the login, the portal displays again the login page with its input fields empty.
    Thus, I can´t to login on the Portal!
    Thanks

    Ricardo: are you accessing Portal using a IP address ? or a domain ?
    When I tried access by IP adress had a similar problem.
    perhaps....
    saludos.
    Leandro

  • If user login in portal we need to assign him, the  perticular system

    Hi all,
    i have the requirement
    if user logins in portal, depending on the user we need to assign him a system( bapi or rfc),
    the user database is maintained in a table in MDM. if an user login in portal it should check in MDM to which region(america, asia.europe....) it belog,s to. according to that we need to assign the system(rfc or bapi). if the user belong's to two regions we need to assign the two links(rfc's or bapi's) regions,
    help me in doing step by step
    Thanks in advance
    Best Regards
    charan

    Hi Charan,
    This is same thread as - Depending on the user we need to assign the system
    Regards,
    Sen

  • Error: "The page cannot be displayed"  when trying to login to portal

    Hi All;
    I can not login to portal, when I click login in portal home page
    http:<server_name>/pls/portal , the sso login screen will never come up, producing an error The page cannot be displayed
    http://:<server_name>/pls/portal/PORTAL.wwsec_app_priv.login?p_requested_url=PORTAL.home&p_cancel_url=PORTAL.home
    BI Components:
    Portal:portal is up and running.
    Http Server is up and running.
    OC4J_Portal is up and running
    Any one has an idea ?
    Thanks.

    Try the troubleshooting documentation:
    - http://download.oracle.com/docs/cd/B14099_19/portal.1014/b19305/cg_app_k.htm#sthref2513
    Mick.

  • Not able to login into portal

    Hi,
    from today morning our user facing problem,
    no one can login into portal, when use enter user id and password in logon page then press to login, the logon page appear agains without any message?
    what could be the reason?
    EP version 7.0
    database  : SQL 2005
    regards,
    kinjal

    HI,
    look like problem with keystorage.
    open J2EE visual Admin tool from following location
    <drive:>\usr\sap\SID\JC<inst_no>\j2ee\admin\go.bat
    connect it.
    expand server -> services -> click on Key Storage -> under view select TicketKeystore
    delete SAPLogonTicketKeypair and SAPLogonTicketKeypair-cert and create it again with CN=SID,OU=SAP Web As,O=SAP Trust Community,C=IN
    C= your country
    restart the portal server.
    regards,
    kaushal

  • Unable to login to Portal

    I re-created the SAPLogonTicketKeypair as per SAP note 983156( Regenerate SAP Logon Tikcket in AS-JAVA), since then i am not able to login to Portal.
    It gives me User authentication failed as error.
    I believe that while genarating certificate, i gave some faulty parameters.
    Firstly, i should not have followed the SAP notes instructions, since AS-JAVA and AS-ABAP are on diffrent hosts.
    Could somebody help me with the right way to generate the certificate.
    Regards
    Govind

    Hi Govind,
    Please remove SAPLogonTicketKeypair and create new SAPLogonTicketKeypair
    then restart the engine.
    now you can loginto the portal.
    <b>Reward points;if it help.</b>
    Thanks,
    Nagaraju

  • Administrator Not able to login Into Portal

    Hi,
    Adminitsrator not able to login into Portal system. I could access succesfully in visual admin .
    Other users can enter in portal screen. I have reset administrator password even then not able to login..
    - Kritene

    Hi Kristene,
       The admin user can get locked due to numerous unsuccessful logon attempts. To correct this situation, you have to use an emergency user SAP*. In the SAP Library, use the following path: "SAP Library -> SAP NetWeaver Library -> SAP NetWeaver by Key Capability -> Security -> Identity Management -> User Management Engine -> Administration of Users, Groups, and Roles -> Activating the Emergency User".
    Log on to the Visual Administrator using the emergency user and unlock the Administrator user. Afterwards, deactivate the emergency user.
    Regards,
    Pooja.

Maybe you are looking for