PGP Command Line License Fails to Authorize
| Article:TECH149419 | | | Created: 2009-05-14 | | | Updated: 2011-02-05 | | | Article URL http://www.symantec.com/docs/TECH149419 |
Problem
Issue
When attempting to authorize a PGP Command Line license using the pgp --license-authorize command for a license which does not have organization name, the license fails to authorize. When authorizing a PGP Command Line licensed the following options are required when executing the command:Required
| --license-name <Name> | Where <Name> is your name or a descriptive name. |
| --license-organization <Org> | Where <Org> is the name of your company. |
| --license-number <Number> | Where <Number> is a valid license number. |
Optional
| --license-email | Where <EmailAddress> is a valid email address, generally the email address of the PGP Command Line administrator. |
Example
pgp --license-authorize --license-name "Alice Cameron" --license-organization "Example Corporation" --license-number "aaaaa-bbbbb-ccccc-ddddd-eeeee-fff" --license-email "acameron@example.com"
Solution
Resolution(s)
When the --license-organization is blank the --license-organization section of the command must include a space within the quotation marks e.g. " ". If the command does not include a space, the license authorization will fail.Example
pgp --license-authorize --license-name "Alice Cameron" --license-organization " " --license-number "aaaaa-bbbbb-ccccc-ddddd-eeeee-fff" --license-email "acameron@example.com"
|
|
Legacy ID
1409
Article URL http://www.symantec.com/docs/TECH149419
Terms of use for this information are found in Legal Notices
Thank you.