RT CLI login

Hi,

I’m trying to use RT CLI to issue several commands however it asks for a
password and none of the ones I initially generated are working. Does the
rt cli program use the root password to work? I get an error (302) found
each time I attempt a login.

Sincerely,

Hi Dave,

There are two ways to authenticate for the RT CLI.

The first is environment variables RTUSER and RTPASSWD

The second is an RT Config file .rtrc in your user’s home directory:
server http://your.rt4.installation http://your.rt4.installation/
user your.rtusername
passwd your rt password

I would verify that you can login to RT with your credentials before using the CLI if you have doubts as to their validity. You can use any user with the CLI, but you will be limited by their permissions. Generally it is recommended to make a user specifically for use with the CLI so you can grant only the permissions that you need.

You can take a look at the wiki here for more information: http://requesttracker.wikia.com/wiki/CLI http://requesttracker.wikia.com/wiki/CLI

Thank you,
Dustin> On Apr 29, 2016, at 1:20 PM, Dave Florek dave.a.florek@gmail.com wrote:

Hi,

I’m trying to use RT CLI to issue several commands however it asks for a password and none of the ones I initially generated are working. Does the rt cli program use the root password to work? I get an error (302) found each time I attempt a login.

Sincerely,

RT 4.4 and RTIR Training Sessions https://bestpractical.com/training

  • Washington DC - May 23 & 24, 2016

signature.asc (801 Bytes)

Good afternoon,

Thanks for the response. I’m not seeing the .rtrc file in my home
directory. I added the username, password and URL via environment variables
and I’m now receiving the following new error message:

Server error: Can’t connect to :443 (certificate
verify failed)

                  (500)On Fri, Apr 29, 2016 at 2:02 PM, Dustin Graves <dustin@bestpractical.com> wrote:

Hi Dave,

There are two ways to authenticate for the RT CLI.

The first is environment variables RTUSER and RTPASSWD

The second is an RT Config file .rtrc in your user’s home directory:

server http://your.rt4.installation
user your.rtusername
passwd your rt password

I would verify that you can login to RT with your credentials before using
the CLI if you have doubts as to their validity. You can use any user with
the CLI, but you will be limited by their permissions. Generally it is
recommended to make a user specifically for use with the CLI so you can
grant only the permissions that you need.

You can take a look at the wiki here for more information:
http://requesttracker.wikia.com/wiki/CLI

Thank you,
Dustin

On Apr 29, 2016, at 1:20 PM, Dave Florek dave.a.florek@gmail.com wrote:

Hi,

I’m trying to use RT CLI to issue several commands however it asks for a
password and none of the ones I initially generated are working. Does the
rt cli program use the root password to work? I get an error (302) found
each time I attempt a login.

Sincerely,

RT 4.4 and RTIR Training Sessions https://bestpractical.com/training

  • Washington DC - May 23 & 24, 2016

Hi,

So, I created the .rtrc file as requested but I’m still receiving the
following:

rt: Server error: Can’t connect to localhost:443 (certificate verify
failed) (500)

How do I allow the RT CLI program to accept https connection certificates
and/or what would be the easiest way to drop https to login via RTCLI?

Thanks,On Mon, May 9, 2016 at 2:26 PM, Dave Florek dave.a.florek@gmail.com wrote:

---------- Forwarded message ----------
From: Dave Florek dave.a.florek@gmail.com
Date: Wed, May 4, 2016 at 1:00 PM
Subject: Re: [rt-users] RT CLI login
To: Dustin Graves dustin@bestpractical.com
Cc: rt-users@lists.bestpractical.com

Good afternoon,

Thanks for the response. I’m not seeing the .rtrc file in my home
directory. I added the username, password and URL via environment variables
and I’m now receiving the following new error message:

Server error: Can’t connect to :443 (certificate
verify failed)

                  (500)

On Fri, Apr 29, 2016 at 2:02 PM, Dustin Graves dustin@bestpractical.com wrote:

Hi Dave,

There are two ways to authenticate for the RT CLI.

The first is environment variables RTUSER and RTPASSWD

The second is an RT Config file .rtrc in your user’s home directory:

server http://your.rt4.installation
user your.rtusername
passwd your rt password

I would verify that you can login to RT with your credentials before
using the CLI if you have doubts as to their validity. You can use any user
with the CLI, but you will be limited by their permissions. Generally it is
recommended to make a user specifically for use with the CLI so you can
grant only the permissions that you need.

You can take a look at the wiki here for more information:
http://requesttracker.wikia.com/wiki/CLI

Thank you,
Dustin

On Apr 29, 2016, at 1:20 PM, Dave Florek dave.a.florek@gmail.com wrote:

Hi,

I’m trying to use RT CLI to issue several commands however it asks for a
password and none of the ones I initially generated are working. Does the
rt cli program use the root password to work? I get an error (302) found
each time I attempt a login.

Sincerely,

RT 4.4 and RTIR Training Sessions https://bestpractical.com/training

  • Washington DC - May 23 & 24, 2016

I ran into this issue and it had to do with an underlying Perl module
requiring certificates to be verified (i.e., not self-signed) when using
SSL. Perhaps it was LWP::UserAgent but I cannot remember for sure. I
chose to fix it by purchasing and installing an inexpensive but valid cert.
That made the problem go away.On Mon, May 23, 2016 at 1:36 PM, Dave Florek dave.a.florek@gmail.com wrote:

Hi,

So, I created the .rtrc file as requested but I’m still receiving the
following:

rt: Server error: Can’t connect to localhost:443 (certificate verify
failed) (500)

How do I allow the RT CLI program to accept https connection certificates
and/or what would be the easiest way to drop https to login via RTCLI?

Thanks,

On Mon, May 9, 2016 at 2:26 PM, Dave Florek dave.a.florek@gmail.com wrote:

---------- Forwarded message ----------
From: Dave Florek dave.a.florek@gmail.com
Date: Wed, May 4, 2016 at 1:00 PM
Subject: Re: [rt-users] RT CLI login
To: Dustin Graves dustin@bestpractical.com
Cc: rt-users@lists.bestpractical.com

Good afternoon,

Thanks for the response. I’m not seeing the .rtrc file in my home
directory. I added the username, password and URL via environment variables
and I’m now receiving the following new error message:

Server error: Can’t connect to :443 (certificate
verify failed)

                  (500)

On Fri, Apr 29, 2016 at 2:02 PM, Dustin Graves dustin@bestpractical.com wrote:

Hi Dave,

There are two ways to authenticate for the RT CLI.

The first is environment variables RTUSER and RTPASSWD

The second is an RT Config file .rtrc in your user’s home directory:

server http://your.rt4.installation
user your.rtusername
passwd your rt password

I would verify that you can login to RT with your credentials before
using the CLI if you have doubts as to their validity. You can use any user
with the CLI, but you will be limited by their permissions. Generally it is
recommended to make a user specifically for use with the CLI so you can
grant only the permissions that you need.

You can take a look at the wiki here for more information:
http://requesttracker.wikia.com/wiki/CLI

Thank you,
Dustin

On Apr 29, 2016, at 1:20 PM, Dave Florek dave.a.florek@gmail.com wrote:

Hi,

I’m trying to use RT CLI to issue several commands however it asks for a
password and none of the ones I initially generated are working. Does the
rt cli program use the root password to work? I get an error (302) found
each time I attempt a login.

Sincerely,

RT 4.4 and RTIR Training Sessions https://bestpractical.com/training

  • Washington DC - May 23 & 24, 2016

RT 4.4 and RTIR Training Sessions https://bestpractical.com/training

  • Los Angeles - September, 2016

If it is LWP::UserAgent (I wish I could recall) you might try adding this
to your environment (e.g., add it to .bash_profile or .bash_rc)

export PERL_LWP_SSL_VERIFY_HOSTNAME=0On Sat, May 28, 2016 at 12:24 PM, John Andersen john@yvig.com wrote:

I ran into this issue and it had to do with an underlying Perl module
requiring certificates to be verified (i.e., not self-signed) when using
SSL. Perhaps it was LWP::UserAgent but I cannot remember for sure. I
chose to fix it by purchasing and installing an inexpensive but valid cert.
That made the problem go away.

On Mon, May 23, 2016 at 1:36 PM, Dave Florek dave.a.florek@gmail.com wrote:

Hi,

So, I created the .rtrc file as requested but I’m still receiving the
following:

rt: Server error: Can’t connect to localhost:443 (certificate verify
failed) (500)

How do I allow the RT CLI program to accept https connection certificates
and/or what would be the easiest way to drop https to login via RTCLI?

Thanks,

On Mon, May 9, 2016 at 2:26 PM, Dave Florek dave.a.florek@gmail.com wrote:

---------- Forwarded message ----------
From: Dave Florek dave.a.florek@gmail.com
Date: Wed, May 4, 2016 at 1:00 PM
Subject: Re: [rt-users] RT CLI login
To: Dustin Graves dustin@bestpractical.com
Cc: rt-users@lists.bestpractical.com

Good afternoon,

Thanks for the response. I’m not seeing the .rtrc file in my home
directory. I added the username, password and URL via environment variables
and I’m now receiving the following new error message:

Server error: Can’t connect to :443 (certificate
verify failed)

                  (500)

On Fri, Apr 29, 2016 at 2:02 PM, Dustin Graves <dustin@bestpractical.com wrote:

Hi Dave,

There are two ways to authenticate for the RT CLI.

The first is environment variables RTUSER and RTPASSWD

The second is an RT Config file .rtrc in your user’s home directory:

server http://your.rt4.installation
user your.rtusername
passwd your rt password

I would verify that you can login to RT with your credentials before
using the CLI if you have doubts as to their validity. You can use any user
with the CLI, but you will be limited by their permissions. Generally it is
recommended to make a user specifically for use with the CLI so you can
grant only the permissions that you need.

You can take a look at the wiki here for more information:
http://requesttracker.wikia.com/wiki/CLI

Thank you,
Dustin

On Apr 29, 2016, at 1:20 PM, Dave Florek dave.a.florek@gmail.com wrote:

Hi,

I’m trying to use RT CLI to issue several commands however it asks for
a password and none of the ones I initially generated are working. Does the
rt cli program use the root password to work? I get an error (302) found
each time I attempt a login.

Sincerely,

RT 4.4 and RTIR Training Sessions https://bestpractical.com/training

  • Washington DC - May 23 & 24, 2016

RT 4.4 and RTIR Training Sessions https://bestpractical.com/training

  • Los Angeles - September, 2016

Also not that this is a very unsafe thing to do as it turns off cert
checking for ANY and ALL perl scripts using LWP::UserAgent. A good test
but I don’t recommending operating with this config.On Sat, May 28, 2016 at 12:33 PM, John Andersen john@yvig.com wrote:

If it is LWP::UserAgent (I wish I could recall) you might try adding this
to your environment (e.g., add it to .bash_profile or .bash_rc)

export PERL_LWP_SSL_VERIFY_HOSTNAME=0

On Sat, May 28, 2016 at 12:24 PM, John Andersen john@yvig.com wrote:

I ran into this issue and it had to do with an underlying Perl module
requiring certificates to be verified (i.e., not self-signed) when using
SSL. Perhaps it was LWP::UserAgent but I cannot remember for sure. I
chose to fix it by purchasing and installing an inexpensive but valid cert.
That made the problem go away.

On Mon, May 23, 2016 at 1:36 PM, Dave Florek dave.a.florek@gmail.com wrote:

Hi,

So, I created the .rtrc file as requested but I’m still receiving the
following:

rt: Server error: Can’t connect to localhost:443 (certificate verify
failed) (500)

How do I allow the RT CLI program to accept https connection
certificates and/or what would be the easiest way to drop https to login
via RTCLI?

Thanks,

On Mon, May 9, 2016 at 2:26 PM, Dave Florek dave.a.florek@gmail.com wrote:

---------- Forwarded message ----------
From: Dave Florek dave.a.florek@gmail.com
Date: Wed, May 4, 2016 at 1:00 PM
Subject: Re: [rt-users] RT CLI login
To: Dustin Graves dustin@bestpractical.com
Cc: rt-users@lists.bestpractical.com

Good afternoon,

Thanks for the response. I’m not seeing the .rtrc file in my home
directory. I added the username, password and URL via environment variables
and I’m now receiving the following new error message:

Server error: Can’t connect to :443 (certificate
verify failed)

                  (500)

On Fri, Apr 29, 2016 at 2:02 PM, Dustin Graves < dustin@bestpractical.com> wrote:

Hi Dave,

There are two ways to authenticate for the RT CLI.

The first is environment variables RTUSER and RTPASSWD

The second is an RT Config file .rtrc in your user’s home directory:

server http://your.rt4.installation
user your.rtusername
passwd your rt password

I would verify that you can login to RT with your credentials before
using the CLI if you have doubts as to their validity. You can use any user
with the CLI, but you will be limited by their permissions. Generally it is
recommended to make a user specifically for use with the CLI so you can
grant only the permissions that you need.

You can take a look at the wiki here for more information:
http://requesttracker.wikia.com/wiki/CLI

Thank you,
Dustin

On Apr 29, 2016, at 1:20 PM, Dave Florek dave.a.florek@gmail.com wrote:

Hi,

I’m trying to use RT CLI to issue several commands however it asks for
a password and none of the ones I initially generated are working. Does the
rt cli program use the root password to work? I get an error (302) found
each time I attempt a login.

Sincerely,

RT 4.4 and RTIR Training Sessions https://bestpractical.com/training

  • Washington DC - May 23 & 24, 2016

RT 4.4 and RTIR Training Sessions https://bestpractical.com/training

  • Los Angeles - September, 2016