Header Login not working in NW04

[Former Member]

Hi all ,

We have configured the Login Module Stacks for Using Header Variables

http://help.sap.

com/saphelp_nw04/helpdata/en/d0/a3d940c2653126e10000000a1550b0/frameset.

htm

So if the header variable is not read a Login Window pops up . BUT even

though the header variable seems to be read a Login Window pops up

anyway .

Login Modules Flag Options

EvaluateTicketLoginModule SUFFICIENT {ume.configuration.

active=true}

HeaderVariableLoginModule OPTIONAL {ume.configuration.active=true

, Header=SM_USER}

CreateTicketLoginModule SUFFICIENT {ume.configuration.

active=true}

BasicPasswordLoginModule REQUISITE {}

CreateTicketLoginModule OPTIONAL {ume.configuration.active=true}

When a user logins the DefaultTrace indicates the userid is being read

in the Header=SM_USER BUT the BasicPasswordLoginModule always pops up .

We need users to SSO into the Portal via SM_USER if it is present. What

addtl steps need to be done to do this in NWO4 ????

Authschemes.xml does not seem to work like it did in EP6 SP2 .

Regards

Daniel

[Former Member · Accepted solution]

Daniel,

Did you create a new login module stack and authschemes.xml to reference it, or did you just add the header variable module to an existing stack e.g ticket and leave authscheme.xml untouched?

I did the former for my custom login module and it didnt work, yet when I did the latter with exactly the same code it worked as expected.

Cheers,

Steve

[Former Member · Accepted solution]

Hi Steve ,

tried to change authschemes.xml (added the login modules )but after that I couldn't login ...got "Header variable is defined " message . So authschemes.xml was being read but I can't work out how to configure it properly in NW04 .

Regards

Daniel

[Former Member · Accepted solution]

Daniel,

Yeah its a black art alright. I would leave authschemes.xml alone, restoring the original file which of course you copied somewhere before changing it, and go into Visual Administrator -> Server node -> Services -> Security Provider and just change an existing module stack such as 'ticket' that is already referenced from authschemes.xml.

I added my login module to 'ticket' and it worked fine, but when I created a new stack and referenced this from a new authschemes created from scratch it didnt work properly

Cheers,

Steve

[Former Member · Accepted solution]

Hi Steve ,

yes I found that a new customized authschemes.xml was the problem although the syntax in it was fine . Using the default one plus adding the Login Modules to ticket template worked .

Glad it's not just me !

Regards

Daniel