cancel
Showing results for 
Search instead for 
Did you mean: 

Custimized logon page doesn't work after upgrade

former_member232095
Participant
0 Kudos

Hi experts,

We have custimized the portal logon page, and during an upgrade it is no longer working. It is back to the standard logon page.

We have created our own .par file and deplyoed it (it is still there after the upgrade) and in the "direct editing" tab in the portal we can still see that the login.authschemes.definition.file is pointing towards our own developed .xml file.

Our customized page has worked fine for a long time, so I am puzzled why it does'nt work after the upgrade. If we had changed any standard SAP, I would understand that things would be overwritten, but we haven't...

It may be worth mentioning that the uploader .par file was marked as 'not installed' after the upgrade. I just clicked 'install'...

Does anyone have any idea of what we should do?

1: Get the customized logon page working again and

2: How to prevent this from happening again?

Regards,

Stina.

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi Stina,

It could be a Portal memory issue. We had the same problem on a previous project I worked on. As soon as we migrated everything to PROD the Portal Logon screen stopped working. Basis cleared up some space on the Portal server and it seemed to resolve the issue.

It's worth a try.

Oloy.

former_member232095
Participant
0 Kudos

Hi Oloy,

Our basis-people says there is plenty of memory the portal server. But it was worth a try!

Any other suggestions, anyone?

Many thanks!

Regards,

Stina

former_member232095
Participant
0 Kudos

Anyone else with any good ideas?

Our custom authschemes.xml file has been validated, and the .par file has, as previous mentioned, been deployed.

Does anyone know of any way to confirm that the .par file is being used by the .xml file? Could this be the breaking point? Anyone with any good ideas on how to verify that?

All help is highly appreciated, and rewarded:)

Regards,

Stina.

former_member232095
Participant
0 Kudos

Got it working.

We had to delete our custom .par and .xml file, restart the server (so that the standard login page worked fine), and then uploaded the .par file + uploaded the .xml file again.

Maybe it was a cache thing...

Thanx for the advises

- Stina.

Former Member
0 Kudos

Hello,

Have you tried redeploying the par after the upgrade?

Roy

former_member232095
Participant
0 Kudos

Hi Roy,

Yes, unfortunately I have tried that...

Any other suggestions?

- stina