[rt-users] Automatically Set "Let this user be granted rights"
Chris Ditri
Cditri at experi-metal.com
Wed Apr 9 14:27:01 EDT 2014
Hi Kevin,
The mapping was just the default in the config file (on a debian wheezy system). I'm not sure how it is dangerous though... can you elaborate?
You are correct, I didn't show a select statement from the db. I wasn't aware that would be helpful. I just know the log file was saying the email already exists (and it does, because it was imported through ldapimport). All the users were populated in the rt users screen from the import, after all. The thing I didn't understand was why rt didn't recognize the user as already existing. It still wanted to make a new one. Why wouldn't it just say, "Oh jjjameson, I know him, let me check his password against AD... Yep... there he is. Access granted." Instead, it seems like it is saying "Oh, jjjameson, I have no record of him (even though it exists). Let me check AD... Oh, there he is, now let's make him a user in rt... wait a minute, his email address is already in use, I guess you are SOL here." Of course it is in use! It was imported, afterall :).
I'm sure there is a logical explanation for this... but I'm afraid this is moot now. I restored a backup of the machine to the time just prior to the ldapimport. I am way past deadline on this project, and I need to get it rolled-out. It turns out that the import is not as important as I initially thought, so I think I can get away without it.
I appreciate the assistance though, very much.
Thank you.
-Chris
-----Original Message-----
From: rt-users-bounces at lists.bestpractical.com [mailto:rt-users-bounces at lists.bestpractical.com] On Behalf Of Kevin Falcone
Sent: Wednesday, April 09, 2014 1:17 PM
To: rt-users at lists.bestpractical.com
Subject: Re: [rt-users] Automatically Set "Let this user be granted rights"
On Wed, Apr 09, 2014 at 08:10:21AM -0400, Chris Ditri wrote:
> Actually no. I didn't want to cron it until I'm sure it is working. I've just been running it manually.
>
> This is interesting though... I just noticed that the errors in the
> logs are the same now regardless of if I use the correct password for
> the user or not. So, logging in as jjjameson with the correct
> password, and an incorrect one gives me the following:
RT-Authen-ExternalAuth will actually try and create the user that you try to log in as, since it exists in LDAP. This is old/known behavior.
I have no idea if it's the root of your problem, but your
'attr_match_list' => [
'Name',
'EmailAddress',
'RealName',
'WorkPhone',
'Address2'
],
is quite dangerous and frankly wrong, since it should only be things that are unique to a user, generally that's Name and EmailAddress.
Also, in a quick review, I don't see where you've shown select * from Users where EmailAddress = 'jjjameson at my-company.com'
so that the list can see what the existing user which is conflicting looks like.
-kevin
>
> [Wed Apr 9 11:56:39 2014] [debug]: Attempting to use external auth
> service: My_LDAP
> (/usr/share/request-tracker4/plugins/RT-Authen-ExternalAuth/lib/RT/Aut
> hen/ExternalAuth.pm:172) [Wed Apr 9 11:56:39 2014] [debug]: Calling
> UserExists with $username (jjjameson) and $service (My_LDAP)
> (/usr/share/request-tracker4/plugins/RT-Authen-ExternalAuth/lib/RT/Aut
> hen/ExternalAuth.pm:213) [Wed Apr 9 11:56:39 2014] [debug]:
> UserExists params:
> username: jjjameson , service: My_LDAP
> (/usr/share/request-tracker4/plugins/RT-Authen-ExternalAuth/lib/RT/Aut
> hen/ExternalAuth/LDAP.pm:299) [Wed Apr 9 11:56:39 2014] [debug]: LDAP
> Search === Base: ou=COMPANY USERS,dc=my-company,dc=com == Filter:
> (&(&)(sAMAccountName=jjjameson)) == Attrs:
> l,cn,st,mail,sAMAccountName,co,streetAddress,postalCode,telephoneNumbe
> r,sAMAccountName,physicalDeliveryOfficeName,sAMAccountName
> (/usr/share/request-tracker4/plugins/RT-Authen-ExternalAuth/lib/RT/Aut
> hen/ExternalAuth/LDAP.pm:329) [Wed Apr 9 11:56:39 2014] [debug]:
> RT::Authen::ExternalAuth::CanonicalizeUserInfo called by
> RT::Authen::ExternalAuth
> /usr/share/request-tracker4/plugins/RT-Authen-ExternalAuth/lib/RT/Auth
> en/ExternalAuth.pm 668 with: Disabled: , EmailAddress: , Gecos:
> jjjameson, Name: jjjameson, Privileged:
> (/usr/share/request-tracker4/plugins/RT-Authen-ExternalAuth/lib/RT/Aut
> hen/ExternalAuth.pm:565) [Wed Apr 9 11:56:39 2014] [debug]:
> Attempting to get user info using this external service: My_LDAP
> (/usr/share/request-tracker4/plugins/RT-Authen-ExternalAuth/lib/RT/Aut
> hen/ExternalAuth.pm:573) [Wed Apr 9 11:56:39 2014] [debug]:
> Attempting to use this canonicalization key: Name
> (/usr/share/request-tracker4/plugins/RT-Authen-ExternalAuth/lib/RT/Aut
> hen/ExternalAuth.pm:587) [Wed Apr 9 11:56:40 2014] [debug]: LDAP
> Search === Base: ou=COMPANY USERS,dc=my-company,dc=com == Filter:
> (&(&)(sAMAccountName=jjjameson)) == Attrs:
> l,cn,st,mail,sAMAccountName,co,streetAddress,postalCode,telephoneNumbe
> r,sAMAccountName,physicalDeliveryOfficeName,sAMAccountName
> (/usr/share/request-tracker4/plugins/RT-Authen-ExternalAuth/lib/RT/Aut
> hen/ExternalAuth/LDAP.pm:217) [Wed Apr 9 11:56:40 2014] [info]:
> RT::Authen::ExternalAuth::CanonicalizeUserInfo returning Address1: ,
> City: , Country: , Disabled: , EmailAddress: jjjameson at my-company.com,
> ExternalAuthId: jjjameson, Gecos: jjjameson, Name: jjjameson,
> Organization: , Privileged: , RealName: J. Jonah, Jameson, State: ,
> WorkPhone: , Zip:
> (/usr/share/request-tracker4/plugins/RT-Authen-ExternalAuth/lib/RT/Aut
> hen/ExternalAuth.pm:651) [Wed Apr 9 11:56:40 2014] [error]: Couldn't
> create user jjjameson: Email address in use
> (/usr/share/request-tracker4/plugins/RT-Authen-ExternalAuth/lib/RT/Aut
> hen/ExternalAuth.pm:237) [Wed Apr 9 11:56:40 2014] [debug]:
> Autohandler called ExternalAuth. Response: (0, No User)
> (/usr/share/request-tracker4/plugins/RT-Authen-ExternalAuth/html/Eleme
> nts/DoAuth:11) [Wed Apr 9 11:56:40 2014] [error]: FAILED LOGIN for
> jjjameson from 192.155.78.155
> (/usr/share/request-tracker4/lib/RT/Interface/Web.pm:740)
>
>
>
>
>
>
>
>
>
>
> -----Original Message-----
> From: rt-users-bounces at lists.bestpractical.com
> [mailto:rt-users-bounces at lists.bestpractical.com] On Behalf Of Jon
> Witts
> Sent: Wednesday, April 09, 2014 7:56 AM
> To: rt-users at lists.bestpractical.com
> Subject: Re: [rt-users] Automatically Set "Let this user be granted rights"
>
> Hi Chris,
>
> I am afraid that I am running out of ideas on this one! I would be tempted to start again with a fresh database once you have both plugins installed and defined in your config correctly. How are you automating the LDAPImport? Have you set up a cron job?
>
> Jon
>
> -----------------------------------------------------
>
> Jon Witts
> Director of Digital Strategy
> Queen Margaret's School
> Escrick Park
> York YO19 6EU
>
> Telephone: 01904 727600
> Fax: 01904 728150
>
> Website: www.queenmargarets.com
>
> -----Original Message-----
> From: Chris Ditri [mailto:Cditri at experi-metal.com]
> Sent: 09 April 2014 12:54
> To: Jon Witts; rt-users at lists.bestpractical.com
> Subject: RE: [rt-users] Automatically Set "Let this user be granted rights"
>
> Hi Jon,
>
> It still is not working. It is, once again, complaining that the email exists already.
> [error]: Couldn't create user jjjameson: Email address in use
> (/usr/share/request-tracker4/plugins/RT-Authen-ExternalAuth/lib/RT/Aut
> hen/ExternalAuth.pm:237)
>
> I don't understand it... It doesn't seem to matter if I use uid, or sAMAccountName either.
>
> -Chris
>
>
>
> Christopher Ditri
> Manager, Information Systems
> Experi-Metal Inc.
> 6385 Wall Street
> Sterling Heights, MI 48312
> Phone: (586) 977-7800
> Fax: (586) 977-6981
> www.experi-metal.com
>
>
>
> Connnect with Us!
>
>
>
>
>
>
>
>
>
>
>
> -----Original Message-----
> From: rt-users-bounces at lists.bestpractical.com
> [mailto:rt-users-bounces at lists.bestpractical.com] On Behalf Of Jon
> Witts
> Sent: Tuesday, April 08, 2014 1:41 PM
> To: rt-users at lists.bestpractical.com
> Subject: Re: [rt-users] Automatically Set "Let this user be granted rights"
>
>
> Chris,
>
> Please keep your responses on the list so that others may benefit or assist.
>
> So what happens when you set your @plugins as I described?
>
> Jon
>
>
> Director of Digital Strategy
>
> Queen Margaret's School
>
> 01904 727600
>
>
>
> http://www.queenmargarets.com
>
>
>
>
>
>
>
>
> From: Chris Ditri [Cditri at experi-metal.com]
>
> Sent: 08 April 2014 6:35 PM
>
> To: Jon Witts
>
> Subject: RE: [rt-users] Automatically Set "Let this user be granted rights"
>
>
>
>
>
>
>
> 4.0.7 - it is what is stable on debian Wheezy.
>
>
>
>
>
>
>
> Christopher Ditri
> Manager, Information Systems
> Experi-Metal Inc.
> 6385 Wall Street
> Sterling Heights, MI 48312
> Phone: (586) 977-7800
> Fax: (586) 977-6981
> www.experi-metal.com
>
>
>
>
>
> Connnect with Us!
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> From: rt-users-bounces at lists.bestpractical.com
> [mailto:rt-users-bounces at lists.bestpractical.com]
> On Behalf Of Jon Witts
>
> Sent: Tuesday, April 08, 2014 12:11 PM
>
> To: rt-users at lists.bestpractical.com
>
> Subject: Re: [rt-users] Automatically Set "Let this user be granted rights"
>
>
>
> What version of RT are you running?
>
> You need to have both plugins (ExternalAuth and LDAPImport) set in your config. Try:
>
> Set( @Plugins, qw(
> RT::Authen::ExternalAuth
>
> RT::Extension::LDAPImport
> ) );
>
> As per the doc on the wiki here:
> http://requesttracker.wikia.com/wiki/SiteConfig
>
>
> Jon
>
>
>
> -----------------------------------------------------
>
> Jon Witts
> Director of Digital Strategy
> Queen Margaret's School
> Escrick Park
> York YO19 6EU
>
> Telephone: 01904 727600
> Fax: 01904 728150
>
> Website:
> www.queenmargarets.com
>
>
>
>
>
> From: Chris Ditri [mailto:Cditri at experi-metal.com]
>
>
> Sent: 08 April 2014 14:46
>
> To:
> rt-users at lists.bestpractical.com
>
> Cc: Jon Witts
>
> Subject: RE: [rt-users] Automatically Set "Let this user be granted rights"
>
>
>
> Hi Jon,
>
> I did add the My_SSO_Cookie thing back, just to troubleshoot. Normally, it is not there. I removed it again, however. I removed the second (redundant) ExternalAuthPriority entry. Thanks for that catch.
>
> Using
> Plugin( "RT::Authen::ExternalAuth" );
> Plugin( "RT::Extension::LDAPImport" );
>
> Doesn't work. I need the "Set(@Plugins..." part.
>
> The interesting thing is that when I do not have "Set(@Plugins, qw(RT::Extension::LDAPImport));" in my config, then I get all the errors in my log file, including the bit about the email already exists (logging is set to debug). If I do have that line in my config, all I get in my log file is "FAILED LOGIN for jjjameson from 118.128.73.X (/usr/share/request-tracker4/lib/RT/Interface/Web.pm:740)". Even though I have the log file set to debug, I get no more output than a simple login failure.
>
> I tried switching uid to sAMAccountName, but that did no better. With no output in the logs, I'm at a complete loss on how to troubleshoot this. I don't know if using the import carries over the password hash into rt's own database, or if it checks it against the ldap/AD server. Since I can see the rest of the user information, perhaps it has to do with the password itself? I don't know...
>
> Thanks again for your help.
>
> -Chris
>
>
>
>
>
>
> From:
>
> rt-users-bounces at lists.bestpractical.com
> [mailto:rt-users-bounces at lists.bestpractical.com]
> On Behalf Of Jon Witts
>
> Sent: Tuesday, April 08, 2014 3:53 AM
>
> To:
> rt-users at lists.bestpractical.com
>
> Subject: Re: [rt-users] Automatically Set "Let this user be granted rights"
>
>
>
> Hi there,
>
> I can only see you setting the ExternalAuth plugin there not the LDAPImport plugin too.
>
> Rather than:
> Set( @Plugins, qw(RT::Authen::ExternalAuth) );
>
> My Plugins section looks like this:
> Plugin( "RT::Authen::ExternalAuth" );
> Plugin( "RT::Extension::LDAPImport" );
>
> Also you are setting
> $ExternalAuthPriority twice, and both times calling ExternalAuths which are not defined ('My_SSO_Cookie', 'My_Oracle','SecondaryLDAP','Other-DB'). I think you should only be doing as follows:
> Set($ExternalAuthPriority, [ 'My_LDAP',
> ]
> );
>
> I have my ldap bind user defined as a fully qualified ldap string rather than just a username...
>
> In your LDAPImport settings try changing:
> Set($LDAPMapping, {Name => 'uid'
>
> To:
> Set($LDAPMapping, {Name => 'sAMAccountName',
>
> And as it appears you are using Microsoft AD for your LDAP server it would probably be worth setting:
> Set($LDAPSizeLimit, 1000);
>
> Too.
>
> Jon
>
>
>
>
> -----------------------------------------------------
>
> Jon Witts
> Director of Digital Strategy
> Queen Margaret's School
> Escrick Park
> York YO19 6EU
>
> Telephone: 01904 727600
> Fax: 01904 728150
>
> Website:
> www.queenmargarets.com
>
>
>
>
>
> From: Chris Ditri [mailto:Cditri at experi-metal.com]
>
>
> Sent: 07 April 2014 22:20
>
> To: Jon Witts;
> rt-users at lists.bestpractical.com
>
> Subject: RE: [rt-users] Automatically Set "Let this user be granted rights"
>
>
>
> Hi Jon, and thanks.
>
> Set($WebDomain, 'rt.my-company.com');
> Set($LDAPHost, 'QZXW-dc.my-company.com'); Set($LDAPUser, 'cn=rtuser,ou=utility,ou=QZXW Users,dc=my-company,dc=com'); Set($LDAPPassword, 'MyPW1234'); Set($LDAPBase, 'ou=QZXW Users,dc=my-company,dc=com'); Set($LDAPFilter, '(&)'); Set($LDAPUpdateUsers, 1);
> Set($LDAPMapping, {Name => 'uid', # required
> EmailAddress => 'mail',
> RealName => 'cn',
> WorkPhone => 'telephoneNumber',
> Organization => 'departmentName'});
> Set($ExternalAuthPriority, [ 'My_LDAP',
> 'My_SSO_Cookie'
> ]
> );
> Set( @Plugins, qw(RT::Authen::ExternalAuth) );
> Set($ExternalInfoPriority, [ 'My_LDAP'
> ]
> );
>
> Set($ExternalServiceUsesSSLorTLS, 0);
>
> Set($AutoCreateNonExternalUsers, 0);
>
> Set($ExternalAuthPriority,['My_LDAP','My_Oracle','SecondaryLDAP','Other-DB']);
> Set($ExternalSettings, { # AN EXAMPLE DB SERVICE
> 'My_LDAP' => { ## GENERIC SECTION
> # The type of service (db/ldap/cookie)
> 'type' => 'ldap',
> # The server hosting the service
> 'server' => 'QZXW-dc.my-company.com',
> ## SERVICE-SPECIFIC SECTION
> # If you can bind to your LDAP server anonymously you should
> # remove the user and pass config lines, otherwise specify them here:
> #
> # The username RT should use to connect to the LDAP server
> 'user' => 'joeadmin at my-company.com',
>
> # The password RT should use to connect to the LDAP server
> 'pass' => 'majorlycrypticpw',
>
> #
> # The LDAP search base
> 'base' => 'ou=QZXW USERS,dc=my-company,dc=com',
> #
> # ALL FILTERS MUST BE VALID LDAP FILTERS ENCASED IN PARENTHESES!
> # YOU **MUST** SPECIFY A filter AND A d_filter!!
> #
> # The filter to use to match RT-Users
> 'filter' => '(&)', ##(I have flip-flopped between this and the one suggested in the generic config, either seems to work)
> # A catch-all example filter: '(objectClass=*)'
> #
> # The filter that will only match disabled users
> 'd_filter' => '',
> # A catch-none example d_filter: '(objectClass=FooBarBaz)'
> #
> # Should we try to use TLS to encrypt connections?
> 'tls' => 1,
> # SSL Version to provide to Net::SSLeay *if* using SSL
> 'ssl_version' => 3,
> # What other args should I pass to Net::LDAP->new($host, at args)?
> 'net_ldap_args' => [ version => 3 ],
> # Does authentication depend on group membership? What group name?
> # What is the attribute for the group object that determines membership?
> # What is the attribute of the user entry that should be matched against group_attr above? (Optional; defaults to 'dn')
> ## RT ATTRIBUTE MATCHING SECTION
> # The list of RT attributes that uniquely identify a user
> # This example shows what you *can* specify.. I recommend reducing this
> # to just the Name and EmailAddress to save encountering problems later.
> 'attr_match_list' => [ 'Name',
> 'EmailAddress',
> 'RealName',
> 'WorkPhone',
> 'Address2'
> ],
> # The mapping of RT attributes on to LDAP attributes
> 'attr_map' => { 'Name' => 'sAMAccountName',
> 'EmailAddress' => 'mail',
> 'Organization' => 'physicalDeliveryOfficeName',
> 'RealName' => 'cn',
> 'ExternalAuthId' => 'sAMAccountName',
> 'Gecos' => 'sAMAccountName',
> 'WorkPhone' => 'telephoneNumber',
> 'Address1' => 'streetAddress',
> 'City' => 'l',
> 'State' => 'st',
> 'Zip' => 'postalCode',
> 'Country' => 'co'
> }
> },
> }
> );
>
> 1;
> my $zone = "UTC";
> $zone=`/bin/cat /etc/timezone`
> if -f "/etc/timezone";
> chomp $zone;
> Set($Timezone, $zone);
>
> Set($rtname, 'rt.my-company.com');
> Set($Organization, 'RT.my-company.com');
>
> Set($CorrespondAddress , 'maintenance at my-company.com');
> Set($CommentAddress , 'maintenance at my-company.com');
> Set($RTAddressRegexp ,
> '^maintenance(-comment)?\@(maintenance|rt)\.(my-company\.com|rt\.my-co
> mpany\.com)$');
>
> Set($WebPath , "/rt");
> Set($WebBaseURL , "http://rt.my-company.com");
>
> Set($LogToSyslog , 'debug');
> Set($LogToScreen , 'info');
>
> Set($LogToFile , 'debug'); #debug is very noisy Set($LogDir, '/var/log/request-tracker4');
> Set($LogToFileNamed , "rt.log"); #log to rt.log
>
> my %typemap = (
> mysql => 'mysql',
> pgsql => 'Pg',
> sqlite3 => 'SQLite',
> );
>
> Set($DatabaseType, $typemap{mysql} || "UNKNOWN");
>
> Set($DatabaseHost, 'localhost');
> Set($DatabasePort, '');
>
> Set($DatabaseUser , 'rtuser');
> Set($DatabasePassword , 'QZXWBuild07');
>
> my $dbc_dbname = 'rtdb'; if ( "mysql" eq "sqlite3" ) { Set
> ($DatabaseName, '' . '/' . $dbc_dbname); } else { Set ($DatabaseName,
> $dbc_dbname); } 1;
>
> Spam -
>
> www.smoothwall.net
>
>
>
>
> DISCLAIMER: This message, including all attachments and/or linked documents, is intended for the exclusive use of the individual or entity to which it is addressed and may contain privileged, proprietary and confidential information. You are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited without permission from the author. This notice serves as a confidentiality marking for the purpose of any confidentiality or nondisclosure agreement. If this message has been received in error, please destroy the original message and all copies without reading it and notify Experi-Metal Inc. immediately via telephone at (586) 977-7800.
>
>
>
> WARNING: This document may contain technical data whose export is restricted by the Arms Export Control Act (Title 22 U.S.C. 2751, et seq.) International Traffic in Arms Regulations (ITAR). Disclosure of any technical data to foreign persons without prior U.S.
> Government authorization is strictly prohibited. Violations of these laws and regulations are subject to severe criminal penalties.
>
>
>
> Thank you very much for your cooperation.
>
>
>
>
> This email has been processed by Smoothwall Anti-Spam -
> www.smoothwall.net
>
>
>
>
> DISCLAIMER: This message, including all attachments and/or linked documents, is intended for the exclusive use of the individual or entity to which it is addressed and may contain privileged, proprietary and confidential information. You are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited without permission from the author. This notice serves as a confidentiality marking for the purpose of any confidentiality or nondisclosure agreement. If this message has been received in error, please destroy the original message and all copies without reading it and notify Experi-Metal Inc. immediately via telephone at (586) 977-7800.
>
>
>
> WARNING: This document may contain technical data whose export is restricted by the Arms Export Control Act (Title 22 U.S.C. 2751, et seq.) International Traffic in Arms Regulations (ITAR). Disclosure of any technical data to foreign persons without prior U.S.
> Government authorization is strictly prohibited. Violations of these laws and regulations are subject to severe criminal penalties.
>
>
>
> Thank you very much for your cooperation.
>
>
>
>
> This email has been processed by Smoothwall Anti-Spam -
> www.smoothwall.net
>
>
>
>
> DISCLAIMER: This message, including all attachments and/or linked documents, is intended for the exclusive use of the individual or entity to which it is addressed and may contain privileged, proprietary and confidential information. You are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited without permission from the author. This notice serves as a confidentiality marking for the purpose of any confidentiality or nondisclosure agreement. If this message has been received in error, please destroy the original message and all copies without reading it and notify Experi-Metal Inc. immediately via telephone at (586) 977-7800.
>
>
>
> WARNING: This document may contain technical data whose export is restricted by the Arms Export Control Act (Title 22 U.S.C. 2751, et seq.) International Traffic in Arms Regulations (ITAR). Disclosure of any technical data to foreign persons without prior U.S.
> Government authorization is strictly prohibited. Violations of these laws and regulations are subject to severe criminal penalties.
>
>
>
> Thank you very much for your cooperation.
>
>
>
>
>
> This email has been processed by Smoothwall Anti-Spam -
> www.smoothwall.net
>
> --
> RT Training - Dallas May 20-21
> http://bestpractical.com/training
>
> DISCLAIMER: This message, including all attachments and/or linked documents, is intended for the exclusive use of the individual or entity to which it is addressed and may contain privileged, proprietary and confidential information. You are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited without permission from the author. This notice serves as a confidentiality marking for the purpose of any confidentiality or nondisclosure agreement. If this message has been received in error, please destroy the original message and all copies without reading it and notify Experi-Metal Inc. immediately via telephone at (586) 977-7800.
>
> WARNING: This document may contain technical data whose export is restricted by the Arms Export Control Act (Title 22 U.S.C. 2751, et seq.) International Traffic in Arms Regulations (ITAR). Disclosure of any technical data to foreign persons without prior U.S. Government authorization is strictly prohibited. Violations of these laws and regulations are subject to severe criminal penalties.
>
> Thank you very much for your cooperation.
>
>
> This email has been processed by Smoothwall Anti-Spam -
> www.smoothwall.net
>
> --
> RT Training - Dallas May 20-21
> http://bestpractical.com/training
>
> DISCLAIMER: This message, including all attachments and/or linked documents, is intended for the exclusive use of the individual or entity to which it is addressed and may contain privileged, proprietary and confidential information. You are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited without permission from the author. This notice serves as a confidentiality marking for the purpose of any confidentiality or nondisclosure agreement. If this message has been received in error, please destroy the original message and all copies without reading it and notify Experi-Metal Inc. immediately via telephone at (586) 977-7800.
>
> WARNING: This document may contain technical data whose export is restricted by the Arms Export Control Act (Title 22 U.S.C. 2751, et seq.) International Traffic in Arms Regulations (ITAR). Disclosure of any technical data to foreign persons without prior U.S. Government authorization is strictly prohibited. Violations of these laws and regulations are subject to severe criminal penalties.
>
> Thank you very much for your cooperation.
> --
> RT Training - Dallas May 20-21
> http://bestpractical.com/training
DISCLAIMER: This message, including all attachments and/or linked documents, is intended for the exclusive use of the individual or entity to which it is addressed and may contain privileged, proprietary and confidential information. You are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited without permission from the author. This notice serves as a confidentiality marking for the purpose of any confidentiality or nondisclosure agreement. If this message has been received in error, please destroy the original message and all copies without reading it and notify Experi-Metal Inc. immediately via telephone at (586) 977-7800.
WARNING: This document may contain technical data whose export is restricted by the Arms Export Control Act (Title 22 U.S.C. 2751, et seq.) International Traffic in Arms Regulations (ITAR). Disclosure of any technical data to foreign persons without prior U.S. Government authorization is strictly prohibited. Violations of these laws and regulations are subject to severe criminal penalties.
Thank you very much for your cooperation.
More information about the rt-users
mailing list