Hello Monks, The process for propagating GPG keys needs to be automated using the following rules. The process currently is manual, and a script should replace the function.
+User creates an a/c on a web application, generate a gpg key pair on his end and send the public key to tutors@ssp.com
+Tech support personnel login to the admin tool (in the web application) and insert this key into the user’s a/c.
+A batch script, import_key.pl runs and updates the keyring with the new key. The key ring is then propagated another batch job, sync_dbm_files.ksh to the front-tier and the maintenance servers.
+Since a valid keyring is present on the front-tier and maintenance, an API connection using valid gpg keys should succeed at this point to both the live and test servers.
A baseline template script covering the steps above would be of great help.
Regards,
Lakke

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.