cancel
Showing results for 
Search instead for 
Did you mean: 

"User ID may not be empty" error dialog even though the user enters the userID and password

0 Kudos

Hi Team,

We are seeing "userID may not be empty" even though user enters the username and password in the SAP WorkManager login screen.

Any suggestions on this please.

Thanks,

Usha

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

what authentication method you are using? USER_AUTH or SSO?

i would say debug the workmanager server class what username and password going to JCO/SAP.

0 Kudos

USER_AUTH_SSO.

Is it linked to authentication method?

Former Member
0 Kudos

yes, it linked to authentication method. If you are using SSO concept please make sure you have done all required configuration like portal and all.

If SSO is not required then please change it to USER_AUTH in JavaBE.ini file.

0 Kudos

Hi Ajitesh,

We have done all configuration for SSO.Please find below config in our file

Can it be because of BYPASS_USERID_CHECK=true

[USER_AUTH_SSO]

; referenced when LOGON_METHOD=USER_AUTH_SSO

; SSO related information for use in LoginModuleSSO to facilitate login to

; an SAP system using tickets from a message server.

;

PORTAL_URL=https://portal.southernwater.co.uk/irj/portal

BYPASS_USERID_CHECK=true

; verificaiton file from the portal. Not required, but if portal names are different from the authenticated username, it will be needed to decode the name.

VERIFICATION_USE=false

;VERIFICATION_FILENAME=verify.pse

;VERIFICATION_PASSWORD=

;VERIFICATION_PASSWORD_ENCODED=false

; key store for client authentication to the server if required

KEY_STORE_USE=true

KEY_STORE_TYPE=jks

KEY_STORE_FILENAME=D:/SAP/Server/configuration/local_smp_keystore.jks

KEY_STORE_PASSWORD=smpAdmin123

KEY_STORE_PASSWORD_ENCODED=false

; trust store for server authentication to the client (accepting only trusted servers to prevent MITM attacks)

TRUST_STORE_USE=true

TRUST_STORE_TYPE=jks

TRUST_STORE_FILENAME=D:/SAP/sapjvm_7/jre/lib/security/cacerts

TRUST_STORE_PASSWORD=changeit

TRUST_STORE_PASSWORD_ENCODED=false

COOKIE=MYSAPSSO2

HTTPTYPE=https

SSL_VERSION=SSLv3

JAVA_SECURITY_DEBUG=false

JAVA_NET_DEBUG=false

; classes to instantiate for the sso client and the callback handler

SSOCLIENT_CLASS=com.mysap.sso.SSOClient

CALLBACK_HANDLER_CLASS=com.syclo.sap.auth.CallbackHandler

Thanks,

Usha

Former Member
0 Kudos

Mohammed,

i don't think its because of the BYPASS_USERID_CHECK. My assumption is when you are trying to authenticate from client it's unable to get SSO ticket from the portal and it is passing the blank value to SAP from Java.

The above configuration looks fine to me. I would suggest to cross check if the portal is returning ticket or not and you are able to login to SAP using the generated ticket or not?



Thanks

Ajitesh