jhullin's account

I still get the same result.

Sure thing: PHOUYJjWId5hEXf2eOAJ955iWhw=

That does work, but I'd be concerned about accidentally leaving out, and therefore deleting, some other signer attributes. Is there a way to zero-in on just the signer's challenge questions using the SDK's RestClient? I assume not.

I had a hunch that the EslClient was holding on to some stale state. I was able to get this working by creating a new instance of EslClient after retrieving the Signer.

		EslClient eslClient = new EslClient( API_KEY, API_URL );

		// get the signer
		Signer signer = eslClient.getPackageService().getSigner(new PackageId(pkgId), signerId);
		
		// display current auth info
		System.out.println(signer.getAuthentication().getMethod());
		System.out.println(signer.getAuthentication().getChallenges());
		
		// clear list and add a new challenge
		Challenge c = new Challenge("Different Question", "Different Answer");
		signer.getChallengeQuestions().clear();
		signer.getChallengeQuestions().add(c);
		
		eslClient = new EslClient( API_KEY, API_URL );	// try creating a new instance
		
		eslClient.getPackageService().updateSigner(new PackageId(pkgId), signer);

		// display updated auth info
		System.out.println(signer.getAuthentication().getMethod());
		System.out.println(signer.getAuthentication().getChallenges());

Thanks for the suggestion, but I have the same issue using SDK 10.13. This link: https://sandbox.e-signlive.com/access/auth?senderAuthenticationToken=OTEyOGE1ZmUtNjgwNy00ZWI1LWJiZmYtOTllZjM4MWMzOTEz&target=https%3A%2F%2Fsandbox.e-signlive.com%2Faccess%2Fdesigner%2Ff05260ea-8a32-413f-85bf-5ca0a2d73949 Yielded this result: https://sandbox.e-signlive.com/servererror/400?messageKey=error.unauthorised.proxyMissing&packageId=