Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’m having a problem with the sessionAsSigner object: it returns “undefined” if one of the custom controls used on an XPage is signed by another user than the XPage. This is annoying (at the least) if you’re working with multiple users on the same application.
Has anyone else experienced this? Or can anyone tell me if this is “by design”?
I have also experienced this.
My guess is that it is ‘as designed’ as the renderer would have no sure way to know who the signer actually is when presented with two or more signing signatures.
Best practice is to always sign the entire application before testing or pushing to production with a signing ID.