[Pulp-list] What is the best way to script our authentication?

[Caoilte O'Connor]

Hi Michael,

Thanks for responding. We are using the command-line interface but we'd
rather not script the password in plain text "pulp-admin login -u
yourusernamehere -p yourpasswordhere" every time and we can't reliably set
it up in advance as the SSL cert expires after 1 week.

Is there any way to configure how long the cert lasts?

Regards

Caoilte



On Wed, Nov 6, 2013 at 2:14 PM, Michael Hrivnak <mhrivnak at redhat.com> wrote:

> Caoilte,
>
> If you're using our command-line interface, you should use its "login"
> feature ($ pulp-admin login -u yourusernamehere). This gives you a
> client-side SSL certificate that automatically gets used by future
> commands. If you're using our REST API directly, you can see authentication
> details here:
>
>
> http://pulp-dev-guide.readthedocs.org/en/pulp-2.2/integration/rest-api/authentication.html
>
> Michael
>
>
> ----- Original Message -----
> From: "Caoilte O'Connor" <caoilte at gmail.com>
> To: pulp-list at redhat.com
> Sent: Monday, November 4, 2013 9:03:36 AM
> Subject: [Pulp-list] What is the best way to script our authentication?
>
> Hi,
> I'm working on some scripts that will use pulp to upload RPMs and copy
> them between repositories.
>
> Is there a better way to authenticate than specifying a password as a
> command line argument? (eg long lasting certs)
>
> Regards
>
> Caoilte
>
> _______________________________________________
> Pulp-list mailing list
> Pulp-list at redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-list/attachments/20131106/3053c61d/attachment.htm>