cancel
Showing results for 
Search instead for 
Did you mean: 

Could able to access E - recruiting part at portal level

Former Member
0 Kudos

Hello,

While logging to portal level with http:
<SID>.<company>.com we could able to access E - recruiting part. we can say SSO is working !!

Where as logging to portal level with http:
<Fully Quailified domain name>: <port>
and Clicking on E - recruiting part gives page to provide login details Why?

Even when we provide login details of backend system of erecruiting. It is saying entries are wrong. Why ?

What is the reason for this behaviour and what are all need to done to login properly. Any User management settings required, What and How ?

Please share your expertise. Thanks in advance.

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos
Where as logging to portal level with http:
<Fully Quailified domain name>: <port> and Clicking on E - recruiting part gives page to provide login details Why?

Do you mean

HTTP --> Portal > HTTPS> E-Rec?

If yes, that's why you got the switch on IE page,

do the connectivity tests in Portal using Support Desk--> SAP Transaction or BSP Page.

Thanks

SM

Former Member
0 Kudos

Hi,

Before checking, How E- recuiting - BSP application is accessible without prompting for logins with http:
pp1.XXX.com ??

Why not with other URL ?

Even though I gave credential, it is not proceeding further as mentioned above.

Please guide us how to access application smoothly w/o prompting login.

Thanks

Former Member
0 Kudos

You should notice related errors in SM21 of the backend system.

What is the client filed it is showing up at the login page?

Thanks

SM

Former Member
0 Kudos

Hi,

It is not showing any client field, userID and paswword field only !!

captured URL as http://<hostname>.XXX.com:<port>/sap/bc/bsp/sap/hrrcf_start_int_application.do?sap-syscmd=nocookie&s...-client=300&sap

Thanks

Ram

Former Member
0 Kudos

Hello Rama,

This happens when HTTPS Switch happens looks likes SSL is not enabled on the system.

If you are using the SSO then it password of the user on back end system should be disabled and front end authentication should be carried to back end system.

If you have the portal user as test123 and SSO enabled then if you have same user in back end system just disable that user password in back end system. The user will authenticate then without asking for password second time.

You can ignore that HTTPS alert warning which you see on webpage.

Regards

Vivek

Former Member
0 Kudos

Hi Vivek,

You are correct. But this issue happening with few users ONLY, who has portal and backend account (same user account)

How to troubleshoot this. Please help me out.

Former Member
0 Kudos

SSO will work only if we have same domain name in backend and front end ..i mean you shoud access system with the same domain as you are calling backend system..

Check this and update.

Regards,

Former Member
0 Kudos

We are not sure on this behavior, with http://pp1.XXXX.com (E-Recruiting) able to access, whereas issue occurs while accessing

E-Recruiting with http://pp1.go.XXXX.com:5XXX0/irj/portal --> invalid behavior.

Error as folows:

1. No swith to HTTPS occured, so it is not secure to send a password. (it is just warning).. But why it is prompting for logins ???

2. If we procvide login details, error comes Client or password is in correct.

Portal (SSO setting):

WAS connection setting are as HTTP only.

    • With link http://pp1.XXXX.com (E-Recruiting) able to access without even prompting for logins (SSO works here)

Thanks

Ram

Former Member
0 Kudos

Hello Friends,

Please help on above issue and share your ideas..!!

Thanks

Ram