OES 11 and Password Self-Service via iManager 2.7

Hi!
OES 11 SP1. Well, not know correct place to ask, but, anyway. Is there a built-in way to setup for users to change their password via iManager? (As I could read-out this option was removed from iManager 2.6 and later. I recall - still have this server running - in NetWare 6.0 (probably iManager 2.0.2) this option was ok. Probably is a good reason for removing it.) If there is not, is ok to use with OES 11 SP1 iManager module from Mr. Wolfgang Schreiber?
More thanks, Alar.

On Thu, 14 Mar 2013 12:56:02 +0000, NovAlf wrote:
> OES 11 SP1. Well, not know correct place to ask, but, anyway. Is there a
> built-in way to setup for users to change their password via iManager?
Not that I know of. You'd be better off using Pwm instead, though.
http://code.google.com/p/pwm/
> If there is not, is ok to use with OES 11 SP1 iManager
> module from Mr. Wolfgang Schreiber?
I don't see why not. Passwords don't care how they get changed.
David Gersic dgersic_@_niu.edu
Knowledge Partner http://forums.netiq.com
Please post questions in the forums. No support provided via email.

Similar Messages

GRC5.2 password self service

Hi Guys,
We plan to start with GRC5.2 with our backend system not having any HR module. However, we do have Travel Expenses setup with relationship of a user mini master.
I understood that in 5.2 Access Enforcer, the password self-service requires infotype (data container), subtype, field and description, from the SAP HR. Can these info also be obtain from a user mini master?
Can I setup the password self service even without HR module (only mini master is setup) within my backend system?
Thanks.
Raymond

Hi Naveen and Amol,
I did checked on the Quick Reference guide and also have a look into the transaction invoved. When I checked on the transaction code (PRMM) for the user mini master, it looks the same as that in transaction PA30 (from the guide). So, theoritically the info from the mini master does looks/match the same as that of the needed info from the HR master records.
I cannot confirm totally on my above statement and was hoping that someone who have tried it to share the experience or is able to guide me with the password self service in 5.2AE.
Thanks Guys..I do welcome more info or advises I can get as it does link critically on the version of GRC AC that the company has decide to implement and password self service is one of the selling point.
P.S: Hi JBS, sry but your links are either not working or pointing to the wrong info.
Thanks.
Raymond

I'm in Afghanistan with limited internet options. I have a wifi service plan I am signed up for however, a log in and password are required via browser log in, not a security key attached to the wifi. Please help...

I'm in Afghanistan with limited internet options. I have a wifi service plan I am signed up for however, a log in and password are required via browser log in, not a security key attached to the wifi (like a hotel). Please help...

the appletv will not be able to work on it's own
you can use a computer or iphone acting the role of hotspot login using it's browser and getting internet access and then sharing it with the appletv
so the appletv sees it as a wifi router it connects to

GRC CUP 5.3 SP16.3 -Password self service limit

Hello Experts,
We came across the issue when integrating Password Self Service(PSS) via challenge response to ask users to answer 2 security questions that they self register the answers to. We noticed that users can even put only one character value in the answers to the security questions, and it accepts it and sends the user the re-set password info to re-log in to the sap backend system via email.
But this is not good bc the security answers should be at least a certain character length with a mixture of upper case ,lower case or numbers..but at least give us the capability to not allow one character answers for the challenge response questions. Is there any1 else who has also faced these issues and know if SAP provided any SAP notes or something to fix the issue. Otherwise, this is not secure enough to reset passwords via one character answers to the challenge response questions.
Thanks and Regards,
A

So, SAP stated that functionality is not available as of right now and to send an enhancement request. I'm surprised they didn't think of this when configuring PSS to ensure the challenge response questions would be well protected and would require at least min character length, etc..

Email notification for AE password Self-Service

Hi Guys,
I have tried to setup AE Password Self-Service and to an extent, its working. However, I do not receive an email notification on the newly changed password.
I have checked my SMTP settings via SCOT and for sure its working as thats the same system which I'm using the FireFighter (which works and sends out email notification).
I've checked on the backend system on the "changed documents" and I see that password was indeed changed by the user which I've used in the background job created in AE.
It seems to me that something is not correctly setup for the communication between AE and the backend system but I cannot figure out which area I should look into (after the above troubleshooting).
If anyone have any suggestions, I would be much appreciated.
P.S: I ahve done the below post-installation configuration:
1) ceated the connectors and tested the connections with success
2) setup verification fields in the password self service (successful as in the initial screen of AE, I'm about to request a change for a new password and the successful message appears)
3) SMTP server in the Workflow is also setup
4) User Data Source is updated (SAP UME)
5) Backgrund jobs on Email Dispatcher and Email Reminder are created
Thanks.
Raymond

Hi Jagat,
Where do we need to modify those parameters suggetsed by you because i can't find any option to change these infotypes in AE.
Kindly suggest, Can you kindly share ADM 955 if you possibly have it with you.
Thanks and Regards,
Siddharth Kaul

CUP v5.3 - Password Self Service - HR Fields Out or Order

Hello everyone,
I have set up Password Self Service in CUP v5.3 for SAP HR. In the Configuration --> Self Service, I have created a few Infotype/Subtype entries. When I go to reset a test user ID's password, the Infotype/Subtype fields appear in a different order than the order in which they are configured in CUP.
What's worse is that even one of the Infotypes is separated from itself by another Infotype/Subtype. For instance, we are testing using IT0009 Bank Details with two Fields: Bank Key and Bank Account Number. Even though I cofigured these two fields to be one after another, the logon screen has them separated by one of the other Infotype/Subtype options.
There doesn't seem to be any logic in the way that the system has adjust the sequence. It's not in alphabetical order, not in numberical order by Infotype, and more importantly, not in the order that I configured them. This will make it very confusing for the users, which of course, defeats the purpose.
Any insight into this?
Thank you!
Johonna

Hello Simon,
That's what I thought was happening at first, but it doesn't appear so. It's not going my the text, technical name , or number for the Infotype, Subtype, or Field Name. What's even stranger ... I deleted them all, then recreated them in the same order that I did the first time, and not only did it not come up in the right sequence, the sequence was different than the first time! Both created the same, both resulted in an incorrect sequence, and yet both came out different!
Even though they are standard HR fields, I might try creating custom versions so that I can force the sequence with the Z01, Z02 naming convention like you did.
Thank you!
Johonna

Bypass security question in Password self service in AC 10

We have configured Password self service in AC10. But as we have integrated with SSO so we do not want a security question registration and its answer to be filled during reset .
So my query, is it possible to bypass the security question and reset the password successfully.

we could have password self service running without security question.
regards
Hemant

CUP-Password Self Service-Email not received by user

Hi,
I confidured SMTP server with Mail server information.
I raised a request for Password Self-service for a User.
Request executed successfuly with a message " Password was reset and send to email id of user"
Password in backend system has reset successfully,
but No Email has received by user regarding reset PW.
What si the problem, why the user not received email? even in CUP it shows that email sent successfully.

Hi,
Yes i scheduled email dispatcher.
Now Email is received by the user.
User received a link for password, when user click on that a blank page with header Password is displayed.
no other information is appearing.
Thanks
Ram.

Password self service in AC10

What is the procedure to roll out Password self service in a 1000+ company. Does it means all the backend system users has to be copied to GRC Production system to use this feature.
If the user wants to reset his password, is it necessarily to login with GRC Password first into GRC and than reset the backend password. If this is the case, than there are less chances that users will remember his GRC password to login into it to reset the password.

A user shouldn't need access to the GRC box itself to use PSS.
Look at the PSS configuration under SPRO->GRC->AC->User Provisioning->Maintain PSS
You can set the authentication source for a user attempting to leverage the PSS feature. You can use the Challenge Questions themselves or another HR system. Also, under that same IMG tree, you will also need to ensure your End User Logon URL is activated and setup properly. This would be the URL individuals would use to access the basic AC features (creating requests, PSS, etc) whom do not have AC accounts themselves.
The key design decisions will be where you will be storing a user's challenge questions and how you will ensure they have their answers registered (ideally part of their onboarding) so that they can use the PSS tool.

Password Self Service

Friends,
We are trying to implement password self service for SAP, AD and Non-SAP systems. The installation and post configuration is complete.
The dispatchers are defined and running sucessfully and the task for Password Reset is defined. The problem is the password reset task/job is not running or picked up by the dispatcher, its always in idle mode. The job logs are also empty.
Are we missing something....we are new to IDM and running 7.1
Regards,
Muthu Kumaran KG

Matt,
Here is the requirement.,
- Password self service for multiple SAP systems and AD
- Password Synchronisation between AD's
Right now I'm trying to configure the PSS. Followed the SAP document and created tasks for password reset, edit authentication questions and password reset failed.
The users will register their authentication questions (http://<server>:port/idm) and after that they do self service (http://<sercer>:port/idm/pwdreset) by answering those questions.
Thanks.
Regards,
Muthu Kumaran KG

Password Self-Service in SUN IDM

Does anyone know if a Password Self-Service is a component of SUN IDM or stand along application? Does SUN offer a seperate Password reset feature?
Thanks!

Sun Identity Manager has built in password recovery functions and you can also use anonymous workflows to produce completely customized processes.

Password self-service workflow message

Hello
Where in configuration do I go to change the password self-service workflow message:
"Your password has been reset. Your password is..."
I know where these messages are for provisioning, but not sure where to go for p/w s-s.
Thanks
JD

Hi,
As Chinmaya mentioned, this message is not easily available to configure. None of the emails are being maintained in backend systems. All of these messages are maintained in NW (front-end) table called Virsa_AE_Message. Go to this table and search for the correspnding message and change it.
FYI, when you upgrade to new SP and upload the initial data xml file, it will overwrite the changes you have made to the message.
Regards,
Alpesh

Error when try access password self service

Hi,
We are on AC5.3, patch level 11. We are trying to setup password self service but we are not very successfull.
When trying to access password self service screen i type in a username and select logon. I then get the following error message:
Application error occurred during request processing.
Details:   java.lang.NullPointerException: null
Exception id: [00215E963384006600005C47000005DC000487177DFC3B51]
The java log is as follows:
2010-05-21 11:05:56,616 [SAPEngine_Application_Thread[impl:3]_4] ERROR Ignorning exception in search by uniqueldapkey, searching by dn
com.sun.jndi.ldap.LdapReferralException: Continuation Reference; remaining name ''
     at com.sun.jndi.ldap.LdapNamingEnumeration.hasMoreReferrals(LdapNamingEnumeration.java:345)
     at com.sun.jndi.ldap.LdapNamingEnumeration.hasMoreImpl(LdapNamingEnumeration.java:224)
     at com.sun.jndi.ldap.LdapNamingEnumeration.hasMore(LdapNamingEnumeration.java:187)
     at com.virsa.ae.service.umi.ldap.LDAPSearchUser.getUserByDN(LDAPSearchUser.java:274)
     at com.virsa.ae.service.umi.ldap.LDAPSearchUser.setManagerDetails(LDAPSearchUser.java:908)
     at com.virsa.ae.service.umi.ldap.LDAPSearchUser.getUsers(LDAPSearchUser.java:695)
     at com.virsa.ae.service.umi.ldap.LDAPSearchUser.getUserById(LDAPSearchUser.java:880)
     at com.virsa.ae.service.umi.ldap.LDAPUserDetailsProvider.getUser(LDAPUserDetailsProvider.java:52)
     at com.virsa.ae.actions.LoginAction.verifyRequestorLoginHandler(LoginAction.java:607)
     at com.virsa.ae.actions.LoginAction.execute(LoginAction.java:102)
     at com.virsa.ae.commons.utils.framework.NavigationEngine.execute(NavigationEngine.java:295)
     at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:431)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
     at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:461)
     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)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(AccessController.java:219)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Please advise.
Regards

2010-05-21 14:54:06,772 [SAPEngine_Application_Thread[impl:3]_33] DEBUG NavigationEngine.java@85:execute() : Current Module: |STARTUP_MODULE| Conversation: |STARTUP_CONVERSATION| Screen: |scrRequestAccess|
2010-05-21 14:54:06,772 [SAPEngine_Application_Thread[impl:3]_33] DEBUG NavigationEngine.java@105:execute() : Module#STARTUP_MODULE#Conversation#STARTUP_CONVERSATION#Screen#scrRequestAccess#Action#verifyRequestorLogin#
2010-05-21 14:54:06,772 [SAPEngine_Application_Thread[impl:3]_33] DEBUG NavigationEngine.java@285:execute() : Handler found:class com.virsa.ae.actions.LoginAction
2010-05-21 14:54:06,772 [SAPEngine_Application_Thread[impl:3]_33] DEBUG LoginAction.java@437:verifyRequestorLoginHandler() : INTO the method
2010-05-21 14:54:06,772 [SAPEngine_Application_Thread[impl:3]_33] DEBUG LDAPAuthenticator.java@66:<init>() : INTO the method : ZACTAD3
2010-05-21 14:54:06,784 [SAPEngine_Application_Thread[impl:3]_33] DEBUG LDAPHandlerFactory.java@30:getHandler() : INTO the method : ldapServerType :ADldapSystemName :ZACTAD3
2010-05-21 14:54:06,784 [SAPEngine_Application_Thread[impl:3]_33] DEBUG UMIFactory.java@116:getAuthenticator() : OUT of the method : Authenticator com.virsa.ae.service.umi.ldap.LDAPAuthenticator@17581758 found for authenticationType:LDAP authenticationSystem:ZACTAD3 authenticationStrategy:
2010-05-21 14:54:06,784 [SAPEngine_Application_Thread[impl:3]_33] DEBUG LDAPAuthenticator.java@66:<init>() : INTO the method : ZACTAD3
2010-05-21 14:54:06,787 [SAPEngine_Application_Thread[impl:3]_33] DEBUG LDAPHandlerFactory.java@30:getHandler() : INTO the method : ldapServerType :ADldapSystemName :ZACTAD3
2010-05-21 14:54:06,787 [SAPEngine_Application_Thread[impl:3]_33] DEBUG UMIFactory.java@116:getAuthenticator() : OUT of the method : Authenticator com.virsa.ae.service.umi.ldap.LDAPAuthenticator@5a8f5a8f found for authenticationType:LDAP authenticationSystem:ZACTAD3 authenticationStrategy:
2010-05-21 14:54:06,788 [SAPEngine_Application_Thread[impl:3]_33] DEBUG Processing interrupted Caused by conversation Interrupted
com.virsa.ae.commons.utils.framework.servlet.InterruptProcessingException: conversation Interrupted
     at com.virsa.ae.commons.utils.framework.NavigationEngine.execute(NavigationEngine.java:299)
     at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:431)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
     at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:461)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
     at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:461)
     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)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(AccessController.java:219)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Caused by:
com.virsa.ae.commons.utils.framework.InterruptConversationException: Forcing user to login
     at com.virsa.ae.actions.LoginAction.verifyRequestorLoginHandler(LoginAction.java:677)
     at com.virsa.ae.actions.LoginAction.execute(LoginAction.java:90)
     at com.virsa.ae.commons.utils.framework.NavigationEngine.execute(NavigationEngine.java:295)
     ... 24 more
2010-05-21 14:54:06,816 [SAPEngine_Application_Thread[impl:3]_35] DEBUG AEFrameworkServlet.java@521:logRequest() :
-- Request dump for Action Path is loadRequestorLoginPage
2010-05-21 14:54:06,817 [SAPEngine_Application_Thread[impl:3]_35] DEBUG AEFrameworkServlet.java@546:logRequest() : -- End Request dump for Action Path is loadRequestorLoginPage
2010-05-21 14:54:06,817 [SAPEngine_Application_Thread[impl:3]_35] DEBUG NavigationEngine.java@85:execute() : Current Module: |STARTUP_MODULE| Conversation: |STARTUP_CONVERSATION| Screen: |scrRequestAccess|
2010-05-21 14:54:06,817 [SAPEngine_Application_Thread[impl:3]_35] DEBUG NavigationEngine.java@105:execute() : Module#STARTUP_MODULE#Conversation#STARTUP_CONVERSATION#Screen#scrRequestAccess#Action#loadRequestorLoginPage#
2010-05-21 14:54:06,817 [SAPEngine_Application_Thread[impl:3]_35] DEBUG NavigationEngine.java@285:execute() : Handler found:class com.virsa.ae.actions.SuccessAction
2010-05-21 14:54:06,817 [SAPEngine_Application_Thread[impl:3]_35] DEBUG NavigationEngine.java@296:execute() : Target returned by execute action: success
2010-05-21 14:54:06,817 [SAPEngine_Application_Thread[impl:3]_35] DEBUG AEFrameworkServlet.java@458:service() : forwarding to:/eu_login.jsp
2010-05-21 14:54:06,818 [SAPEngine_Application_Thread[impl:3]_35] DEBUG AECacheUtil.java@2139:getDropDownList() : INTO the method : hmFA{DE=German, KO=Korean, SK=Slovak, NL=Dutch, IT=Italian, CS=Czech, PT=Portuguese, HR=Croatian, FR=French, PL=Polish, NO=Norwegian, FI=Finnish, ZH=Chinese, HU=Hungarian, JA=Japanese, ES=Spanish, EN=English, DA=Danish, RU=Russian, SV=Swedish}
2010-05-21 14:54:11,067 [SAPEngine_Application_Thread[impl:3]_16] DEBUG AEFrameworkServlet.java@521:logRequest() :
-- Request dump for Action Path is requestorLogin1
2010-05-21 14:54:11,067 [SAPEngine_Application_Thread[impl:3]_16] DEBUG AEFrameworkServlet.java@541:logRequest() : requestType:0::PSS#
2010-05-21 14:54:11,067 [SAPEngine_Application_Thread[impl:3]_16] DEBUG AEFrameworkServlet.java@541:logRequest() : selLanguage:0::#
2010-05-21 14:54:11,067 [SAPEngine_Application_Thread[impl:3]_16] DEBUG AEFrameworkServlet.java@541:logRequest() : j_user:0::PADAM#
2010-05-21 14:54:11,067 [SAPEngine_Application_Thread[impl:3]_16] DEBUG AEFrameworkServlet.java@546:logRequest() : -- End Request dump for Action Path is requestorLogin12010-05-21 14:54:06,772 [SAPEngine_Application_Thread[impl:3]_33] DEBUG NavigationEngine.java@85:execute() : Current Module: |STARTUP_MODULE| Conversation: |STARTUP_CONVERSATION| Screen: |scrRequestAccess|
2010-05-21 14:54:06,772 [SAPEngine_Application_Thread[impl:3]_33] DEBUG NavigationEngine.java@105:execute() : Module#STARTUP_MODULE#Conversation#STARTUP_CONVERSATION#Screen#scrRequestAccess#Action#verifyRequestorLogin#
2010-05-21 14:54:06,772 [SAPEngine_Application_Thread[impl:3]_33] DEBUG NavigationEngine.java@285:execute() : Handler found:class com.virsa.ae.actions.LoginAction
2010-05-21 14:54:06,772 [SAPEngine_Application_Thread[impl:3]_33] DEBUG LoginAction.java@437:verifyRequestorLoginHandler() : INTO the method
2010-05-21 14:54:06,772 [SAPEngine_Application_Thread[impl:3]_33] DEBUG LDAPAuthenticator.java@66:<init>() : INTO the method : ZACTAD3
2010-05-21 14:54:06,784 [SAPEngine_Application_Thread[impl:3]_33] DEBUG LDAPHandlerFactory.java@30:getHandler() : INTO the method : ldapServerType :ADldapSystemName :ZACTAD3
2010-05-21 14:54:06,784 [SAPEngine_Application_Thread[impl:3]_33] DEBUG UMIFactory.java@116:getAuthenticator() : OUT of the method : Authenticator com.virsa.ae.service.umi.ldap.LDAPAuthenticator@17581758 found for authenticationType:LDAP authenticationSystem:ZACTAD3 authenticationStrategy:
2010-05-21 14:54:06,784 [SAPEngine_Application_Thread[impl:3]_33] DEBUG LDAPAuthenticator.java@66:<init>() : INTO the method : ZACTAD3
2010-05-21 14:54:06,787 [SAPEngine_Application_Thread[impl:3]_33] DEBUG LDAPHandlerFactory.java@30:getHandler() : INTO the method : ldapServerType :ADldapSystemName :ZACTAD3
2010-05-21 14:54:06,787 [SAPEngine_Application_Thread[impl:3]_33] DEBUG UMIFactory.java@116:getAuthenticator() : OUT of the method : Authenticator com.virsa.ae.service.umi.ldap.LDAPAuthenticator@5a8f5a8f found for authenticationType:LDAP authenticationSystem:ZACTAD3 authenticationStrategy:
2010-05-21 14:54:06,788 [SAPEngine_Application_Thread[impl:3]_33] DEBUG Processing interrupted Caused by conversation Interrupted
com.virsa.ae.commons.utils.framework.servlet.InterruptProcessingException: conversation Interrupted
     at com.virsa.ae.commons.utils.framework.NavigationEngine.execute(NavigationEngine.java:299)
     at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:431)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
     at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:461)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
     at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:461)
     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)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(AccessController.java:219)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Caused by:
com.virsa.ae.commons.utils.framework.InterruptConversationException: Forcing user to login
     at com.virsa.ae.actions.LoginAction.verifyRequestorLoginHandler(LoginAction.java:677)
     at com.virsa.ae.actions.LoginAction.execute(LoginAction.java:90)
     at com.virsa.ae.commons.utils.framework.NavigationEngine.execute(NavigationEngine.java:295)
     ... 24 more
2010-05-21 14:54:06,816 [SAPEngine_Application_Thread[impl:3]_35] DEBUG AEFrameworkServlet.java@521:logRequest() :

CUP Password Self Service

Hi,
I have some problems with using the password self service.
The user has answered the challenge response and is registered. After losing the password the user tries to access the password self service link. Therefore he has to login - why??? This doesn't makes at all, as the user lost his password! Did I miss a setting or did I misunderstood the functionality???
Best regards,
Christian

Hi Christian,
sure this authentication depends on the "Authentication" configuration, but I wouldn't change this data source as you probably had a reason for choosing a SAP system as data source.
Following things I figured:
- setting the Self-Service to "SAP HR" and configuring the "Disable Verification" to "Password Self-Service" will do exactly what you need: no authentication needed but verification by HR info types. This extra logon before the verification can be disabled like it was in 5.2
Unfortunately you will need an HR system with data configured for all users using PSS
- setting Self-Service to "Challenge Response", by setting the "Disable Verification" to "None" you can disable the questions but NOT the initial logon
I can't really figure why this is working the opposite way for both types of password self-service. Let me know if you find a nice solution. Or did you open an OSS?
Regards,
Daniela

CUP 5.3 Password-Self-Service SP9

Hello all,
since CUP 5.3 SP09, the Password-Self-Service has complety changed.
You need to Login to the System before you can reset the password. The Authentication System is linked to the UME, which is connected to an SAP-System where all approvers have a User.
The PSS is used by all our SAP-Users, not only approvers. So, not all Users have a UserID in the UME.
-> From SP 09, the PSS is not working anymore for most of our users, since a Login to use the PSS is needed.
Due to different errors, we had to patch the system now to SP14.
We have activated SSO as recommended in note 1451616 does not help as not all Users have access to our UME.
Does anyone has similar problems / experiences? And an idea for a workaround?
Thanks a lot
Marco

Hello Kristian,
unfortunatly thats not possible, because the UserIDs in the SAP-Systems are different (we are using personnel-number).
So, regular CUP-requests could not be approved any longer as the approvers have to login with their personnel-ID to approve the requests pending. The LineManager-approver ID is getting read from HR.
It is not possible to choose different UserDataSource to Login for PSS and approvals. And in the new PSS-Version, you can only reset the password for the ID you are logged in.
thanks
Marco

OES 11 and Password Self-Service via iManager 2.7

Similar Messages

Maybe you are looking for