Question/problem about configuring secure sites

I have a question

  1. Update the file including the member.service.* properties to match your environment.

Can you tell me what this means so I can ask our IT guys to do it?

does this mean we need to open these ports, or assign new ports?

membership.service.port is the port to use to access

the membership service for authentication, should be the correct

port for the specified membership.service.protocol


perc.webserver.http.port is the HTTP port of the web server

which services all published pages.


perc.webserver.https.port is the HTTPS port of the web server

which services all published pages.


are these links - login success etc - variables that will pull actual pages from percussion, or links to pages on our site that we named whatever we named them? is the published location of the

page containing the login form. is the location of an

(optional) published page for redirect in cases in which

no secure resource has been requested

and it they are not variables, how can we set up secure sections on more than one web site?

Hi Bob,

Sure, so the main two configuration properties you’ll need to set are “perc.webserver.http.port” and “perc.webserver.https.port”. Your HTTP port will be set to 80 (unless you’re testing this internally on an alternate port), and your HTTPS port should be set to 443 (unless you are using an alternate HTTPS port). Your “membership.service.port” should be the same as your HTTP port. The two login properties are placeholders, and should be overridden when you specify your own paths while setting up secure sections through the UI. Let me know if you have any other questions about this.

Excellent Nathaniel, thanks. But one question remains- if i set the login properties - how can I make secure sections on more than one site? We have 7 sites, 5 need secure sections.


Hey Bob, apologies if I wasn’t clear. When you specify a login page through CM1 for each individual site, publishing that site out will push out a config file containing the new login page path. This new site-specific config file should override what’s present in the file, and that way you can have unique login page paths for each site.