Blogs

When changing the guest OS password of root, you may encounter an Authentication token manipulation error. This message occurs because the /etc/shadow file is not present. You can add the shadow file by entering 'pwconv', then the root password can be set. See the example below.

bash-3.2# passwd
Changing password for user root.
passwd: Authentication token manipulation error

bash-3.2# pwconv
bash-3.2# passwd
Changing password for user root. ...Read More

 

In addition to bug fixes, AXP 1.6.2 adds support for the new SM-SRE-710-K9 and SM-SRE-910-K9 service modules. Additionally, the expiration check of the authorization bundle is no longer enforced in AXP 1.6.2. The authorization bundle, which is provided by Cisco Developer Network, grants permission to run applications on the AXP platform. In addition to security information, the authorization bundle also contains an expiration date. Starting from AXP 1.6.2, the check on this expiration date ...Read More

 

The AXP upgrade process provides key features such as automatic deletion of previously installed files that are not included in the upgrade package. However, in order to not delete previously installed files, the upgrade process requires that previously installed files be included in the upgrade package which can lead to bloated packages. To simply the package and reduce package size, users can create a patch to modify only intended files. For example, if the initial installed package contai ...Read More

 

AXP version 1.6.1 has added support for Simple Network Management Protocol SNMPv2c. SNMP commands used in Cisco AXP are similar to Cisco IOS software SNMP commands. The AXP User Guide provides examples of traps generated by agents in SNMP that are utilized by Cisco AXP. Please review the AXP User Guide section 'System Management using SNMP and CDP' along with the Command Reference Guide for more information.
...Read More

 

In addition to bug fixes, the AXP 1.5.2 maintenance release builds upon AXP 1.5.1- see the blog 'AXP 1.5.1 Release - A Giant Leap Forward' - by adding support for two new service modules. The SRE 700 has a 1.86 GHz cpu, 4 GB Ram, and a 500 GB HD. The SRE 900 offers Raid 1 support, has a 1.86 GHz dual core cpu, 4 GB RAM and 2x500 GB HD. Raid-1 and linear raid can be selected as options at install time. This new hardware runs on the new Cisco Generation 2 routers which require IOS re ...Read More

 

AXP takes a huge step forward by adding new hardware support and software features. I¿ll discuss many of the new hardware and features below.
...Read More

 

After downloading the provided AXP gzipped tar files for your service module, if you are using a windows environment, you might decide to untar the files with WinZip. If this choice is made, caution must be taken because WinZip has a 'TAR file smart CR/LF Conversion ...Read More

 

Showing 7 results.
Items per Page 20
of 1
First Previous Next Last

Forums

« Back to Technical Questions

"Authorization document not found" Error

Combination View Flat View Tree View
Threads [ Previous | Next ]
Post New Thread
"Authorization document not found" Error
Answer
4/18/11 10:25 PM
I installed three packages:

App1 (testdep) - depends on guest_os
App2 (sunjre) - depends on App1 and guest_os (this is installed as an add-on)
App3 (test) - depends on App2 and guest_os (intended to be a regular app-service, but ended up being an add-on like app)

Now I try to uninstall them but get a validation error saying there is not an authorization document for the sunjre package (App2).

=========ERROR MESSAGE BEGINS===============

There are add-on subsystems on uninstall list.
Generating the add-on-uninstall work order :
Validating installed manifests ....
Trying Third Party verification
Validating installed manifest /sw/installed/manifest/test_manifest.sig
Validation Error: Authorization document not found for sunjre
AesopError.AesopInstallerError: Manifest signature validation failed for test_ma
nifest.sig

=========ERROR MESSAGE ENDS=================

With this validation error, I can't add/remove packages.

What to do?
Flag

Re: "Authorization document not found" Error
Answer
1/29/09 4:17 AM as a reply to Johnny Loi.
I am not sure why you are doing a three level dependency. Can you explain what's the usecase?

You can issue software install clean command and reinstall AXP OS.

Edited by: Anurag Gurtu on Jan 28, 2009 5:17 PM
Flag

Re: "Authorization document not found" Error
Answer
1/29/09 4:23 AM as a reply to Johnny Loi.
App1 got the JRE from App2. But the dependency seems reversed. I was trying to see if I can install App3 and get the JRE from App2.

What I'm trying to do is have the JRE installed as an add-on, and if an application needs the Sun JRE, I just tell that application to have dependency on the JRE package.

I tried doing an install clean, but that doesn't work. Apparently, AXP tries to validate the third party applications before doing a clean. So the install failed because of the authorization document isn't found.
Flag

Re: "Authorization document not found" Error
Answer
1/29/09 4:33 AM as a reply to Johnny Loi.
Custom developed 3rd party add-ons are treated in a different way than Cisco add-ons hence you see a reverse dependency, that's part of the current design. If APP2 depends upon APP1 and APP3 depends upon APP2 you will see that VI of APP1 will contain all three APPs as per the design. Hence we suggest developing /packaging self contained application where all components reside in same VI rather than having components installed separately and then specifying dependency.

Can you provide the full syntax of the command you issued? software install clean
Flag

Re: "Authorization document not found" Error
Answer
1/29/09 10:36 PM as a reply to Johnny Loi.
software install clean url ftp://xxx.xxx.xxx.xxx/axp-k9.nme.1.1.1.pkg username xxx password xxx
Flag

Re: "Authorization document not found" Error
Answer
1/30/09 2:00 AM as a reply to Johnny Loi.
I used the AXP helper image to reinstall AXP OS.
Flag

Collateral


No files available