The test signing service, using a different URL, needs a separate certificate, which the main ASF contact person has to issue. He is currently unable to do that due to other issues, but suggests as a workaround, to use the production URL, but there selecting the "test" mode.
Are you able to access the test signing service that way? -Marshall On 1/28/2016 4:42 AM, Peter Klügl wrote: > Ok, I found out that I am not able to use the test signing service but > only the prduction signing service. > > Marshall, do you have an idea how I can extend my role in order to > access the test signing service? Did you see an option when you added me? > > Best, > > Peter > > Am 27.01.2016 um 21:07 schrieb Marshall Schor: >> not in my browser - it forwards the https req to a related site but then says >> Secure connection failed. >> >> Is this what happened with you? >> >> -M >> >> On 1/27/2016 4:24 AM, Peter Klügl wrote: >>> Marshall, are you able to access the test system? >>> >>> https://test-securesigning.websecurity.symantec.com/csportal/ >>> >>> >>> Am 27.01.2016 um 10:17 schrieb Peter Klügl: >>>> Am 26.01.2016 um 22:09 schrieb Marshall Schor: >>>>> On 1/26/2016 5:20 AM, Peter Klügl wrote: >>>>>> ... >>>>>> ect all this info... >>>>>> Should we just copy the implementation to some of our (build) projects? >>>>> It would be good to automate this of course. I think that would take >>>>> using the >>>>> SOAP interface with the Ant script done by the Apache TomCat project. >>>>> However, some basic info on our web site for posterity once we forget how >>>>> this >>>>> all works would be good - pointers to other pages that describe how it all >>>>> works, how to use the test stuff, etc. >>>>> -Marshall >>>>> >>>> Yes, I will create/extend a page once it is up and running. >>>> >>>> Best, >>>> >>>> Peter >>>> >
