Open GoogleCodeExporter opened 9 years ago
[deleted comment]
I'm experiencing this exact same issue. I'll play around with the signing code
to see if I can figure out what the new set of data is.
The only difference is I have a slightly more updated GSA:
System Version: 7.0.14.G.114
Build ID: 10000329.1.4
And I'm connecting from Linux.
Original comment by m...@clayto.com
on 7 May 2013 at 9:42
You need to remove the uar_data and the uam_dir elements (and the whitespace
before each tag), then sign.
Original comment by bobbobbo...@outlook.com
on 8 May 2013 at 2:47
Thanks so much for the help. How did you find out that those elements must be
removed? If there is a DTD or other resource out there for these config files,
I'd be happy to have it.
It looks like the gsa_admin.py I have is already doing these steps during
sign():
1. remove whitespace before <uam_dir>
2. remove uam_dir element from the dom (it's using minidom)
3. sign and insert the signature
4. add <uamdir> back into the dom
I copied the code to do the same for the uar_data element. It's working, based
on the output, but the GSA is still rejecting it with the same error.
Original comment by m...@clayto.com
on 8 May 2013 at 6:56
Original issue reported on code.google.com by
bobbobbo...@outlook.com
on 17 Feb 2013 at 3:03