Changing $Organization in RT_Config

Mike_Friedman · April 3, 2007, 8:10pm

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I’ve consulted the list archives about this, but have not seen a
definitive answer to my specific question, which is:

What are the practical consequences of changing the value of $Organization
in the RT config? This is separate from the question of $rtname, which I
know about.

The comment in RT_Config says that $Organization is “used by the linking
interface to guarantee that ticket URIs are unique and easy to construct”.
Which URIs make use of $Organization?

I’m about to upgrade from RT 3.4.5 to 3.6.3. I’ve done a clean install in
a new environment and plan to move over my existing database that’s been
running with 3.4.5. However, for various reasons (the domain name isn’t
really appropriate any more, for one thing), if possible I’d like the
value of $Organization to better reflect the new auspices under which this
RT will be running.

What kind of things might break if I change the value of $Organization
while continuing to use the same database as before (after upgrading the
schema, of course)?

Thanks.

Mike

Mike Friedman Information Services & Technology
mikef@ack.Berkeley.EDU 2484 Shattuck Avenue
1-510-642-1410 University of California at Berkeley
Socrates and Berkeley Scholars Web Hosting Services Have Been Retired | Web Platform Services http://ist.berkeley.edu

-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.8

iQA/AwUBRhK0060bf1iNr4mCEQLLHgCghSZjoul0gfH90mRGKEA+Gl762boAnA1b
gvPZ0Do4V+oUfwHlQ0WjHsIo
=tY4U
-----END PGP SIGNATURE-----

Jesse_Vincent · April 3, 2007, 10:41pm

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I’ve consulted the list archives about this, but have not seen a
definitive answer to my specific question, which is:

What are the practical consequences of changing the value of
$Organization in the RT config? This is separate from the question
of $rtname, which I know about.

The comment in RT_Config says that $Organization is “used by the
linking interface to guarantee that ticket URIs are unique and easy
to construct”. Which URIs make use of $Organization?

I’m about to upgrade from RT 3.4.5 to 3.6.3. I’ve done a clean
install in a new environment and plan to move over my existing
database that’s been running with 3.4.5. However, for various
reasons (the domain name isn’t really appropriate any more, for one
thing), if possible I’d like the value of $Organization to better
reflect the new auspices under which this RT will be running.

What kind of things might break if I change the value of
$Organization while continuing to use the same database as before
(after upgrading the schema, of course)?

You’ll break all the links between tickets.

Best,
Jesse

PGP.sig (186 Bytes)

Mike_Friedman · April 4, 2007, 9:48pm

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1On Wed, 4 Apr 2007 at 07:41 (+0900), Jesse Vincent wrote:

What kind of things might break if I change the value of $Organization
while continuing to use the same database as before (after upgrading
the schema, of course)?

You’ll break all the links between tickets.

Jesse,

OK, thanks. I guess I can live with the existing value of $Organization.

Mike

Mike Friedman Information Services & Technology
mikef@ack.Berkeley.EDU 2484 Shattuck Avenue
1-510-642-1410 University of California at Berkeley
Socrates and Berkeley Scholars Web Hosting Services Have Been Retired | Web Platform Services http://ist.berkeley.edu

-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.8

iQA/AwUBRhQdPa0bf1iNr4mCEQIXIgCeIChkIcZQAyW9k5nHquDLW9sNm5QAn2eZ
myG7sIVnINWKJAFhzblyMemN
=lAQe
-----END PGP SIGNATURE-----

Mike_Friedman · April 4, 2007, 10:10pm

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

How do I tell RT’s mysql interface where to find my mysql SSL
certificates?.

For the first time ever, I’m going to have my RT database on a remote
server and I want to use SSL. I can see from the mysql manual how to
configure the certs and point to them in my.cnf. But now I’m told by our
db guy that a perl interface to mysql may not make use of my.cnf and, even
if it does, how will it find that file?

In DBD::mysql - MySQL driver for the Perl5 Database Interface (DBI) - metacpan.org, it
says the following:

mysql_read_default_group

These options can be used to read a config file like /etc/my.cnf
or ~/.my.cnf. By default MySQL’s C client library doesn’t use any
config files unlike the client programs (mysql, mysqladmin, …)
that do, but outside of the C client library. Thus you need to
explicitly request reading a config file, as in

 $dsn = "DBI:mysql:test;mysql_read_default_file=/home/joe/my.cnf";
 $dbh = DBI->connect($dsn, $user, $password)

Does this mean I must do something to the RT code to accomplish what I
want? I see nothing in RT_Config about db certs, so there must be some
other way to tell RT’s mysql interface how to use them. Is there anything
in DBIx::SearchBuilder that would deal with this SSL issue?

I’m sure I’m overlooking something obvious.

BTW: my my.cnf file is not in a standard place. It must be in my own
home directory because I’m running on a virtual private server where
everything must be in my home directory.

Thanks.

Mike

Mike Friedman Information Services & Technology
mikef@ack.Berkeley.EDU 2484 Shattuck Avenue
1-510-642-1410 University of California at Berkeley
Socrates and Berkeley Scholars Web Hosting Services Have Been Retired | Web Platform Services http://ist.berkeley.edu

-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.8

iQA/AwUBRhQiX60bf1iNr4mCEQIU4gCeOY90ZCMy78R2C1vUcE/QlmVJOboAoLXm
YoGvCKtz45ZHo4cTf5hfOyrV
=yWdM
-----END PGP SIGNATURE-----

Mike_Friedman · April 6, 2007, 6:05pm

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Normally I would wait longer than a couple of days for a reply before
reposting a question to this list, so I apologize for seeming impatient.
But I find it hard to believe that running RT against a remote mysql db
using SSL is such an uncommon thing for people to do. So, surely many
others already know the answer to my question.

When I consult the list archives, the RT wiki and google in general, all I
find about SSL and RT relates to the use of SSL with Apache and the web
interface. But I’m interested in the mysql SSL interface. From what I
can tell thus far, perl DBI/DBD code doesn’t honor the mysql my.cnf config
file by default, so one must insert perl code(*) to cause it to do so. How
else can I inform the mysql client where to find the mysql server SSL
certificate?

(*) According to the CPAN docs for DBD::mysql:

mysql_read_default_group

These options can be used to read a config file like /etc/my.cnf
or ~/.my.cnf. By default MySQL’s C client library doesn’t use any
config files unlike the client programs (mysql, mysqladmin, …)
that do, but outside of the C client library. Thus you need to
explicitly request reading a config file, as in

 $dsn = "DBI:mysql:test;mysql_read_default_file=/home/joe/my.cnf";
 $dbh = DBI->connect($dsn, $user, $password)

Do I need to add code like the first line above somewhere in RT? If so,
where? Or are there some values that can be put into RT_SiteConfig.pm
that I don’t know about? This is all in reference to RT 3.6.3.

I hope someone can help.

Thanks.

Mike

Mike Friedman Information Services & Technology
mikef@ack.Berkeley.EDU 2484 Shattuck Avenue
1-510-642-1410 University of California at Berkeley
Socrates and Berkeley Scholars Web Hosting Services Have Been Retired | Web Platform Services http://ist.berkeley.edu

-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.8

iQA/AwUBRhaMAK0bf1iNr4mCEQIOTwCgiTXcEZn1dX8CiGK/mPysQcfYMJgAoK/w
4qjh4nFyJ2ZuzanzUu36KaG8
=Pby1
-----END PGP SIGNATURE-----