JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for LCG-ROLLOUT Archives


LCG-ROLLOUT Archives

LCG-ROLLOUT Archives


LCG-ROLLOUT@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

LCG-ROLLOUT Home

LCG-ROLLOUT Home

LCG-ROLLOUT  December 2012

LCG-ROLLOUT December 2012

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: APEL_PUBLISH_USER_DN :: is it required or mandatory?

From:

Tiziana Ferrari <[log in to unmask]>

Reply-To:

LHC Computer Grid - Rollout <[log in to unmask]>

Date:

Mon, 3 Dec 2012 23:44:15 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (86 lines)

Hi Adrian

> ok.. If the feedback from VOs and especially from WLCG VOs was ok i have
> nothing to say on this .. maybe i missed the mails when the VOs
> communicated to their contributors the results of this discussions.

"Grid Policy on the Handling of User-Level Job Accounting Data" hasn't 
been changed since its approval in 2009 and it was defined in 
collaboration with WLCG: "Imported from JSPG policy document with the
same title. No changes to wording were made. See 
https://edms.cern.ch/document/855382 (V1.0, dated 6 Aug 2009) for the 
old JSPG document."
(https://documents.egi.eu/document/85)
This policy was defined after consultation with many legal experts.
Because of wrong configurations, many sites were not enforcing the 
policy, this explains the ticket received by your site from EGI.

>> The  Grid Policy on the Handling of User-Level Job Accounting Data says:
>> <<Each site is responsible for sending its accounting records on a
>> regular basis, e.g. daily, with at least user DNs encrypted in
>> transport, to a central data base defined by the Grid.>> and
>> <<Access to a portal that allows the decoding of the anonymised name
>> into a person’s DN is restricted to individuals in the VO appointed to
>> be VO Resource Managers.>>
>>
>> That means that users are aware of the fact that the accounting data can
> where is this meaning in the paragraph above? Unless is written
> explicitly in their AUP the users dont know.

The user signs a AUP at the time of registering the membership to a VO.
The is the generic VO AUP template :
"Members and Managers of the VO agree to be bound by the Grid Acceptable 
Use Policy, the various security policies and  other relevant Grid 
policies, and to use the Grid only in the furtherance of the stated goal 
of the VO.” (from the Virtual Organization Registration Security Policy 
https://documents.egi.eu/document/78) .

Among the "Various security policies" we have the VO operation policy (
http://documents.egi.eu/document/77 ) which claims:
"You shall comply with the Grid security policies, the VO AUP and any 
archival, accounting and logging requirements. You shall periodically 
assess, at least once per year, your compliance with these policies and 
inform the Grid Security Officer of any violations encountered in the 
assessment, and correct such violations forthwith"

>> VO use the accounting portal to access the data, how are VOs supposed to
>> access accounting data if this information is not provided to the
>> repository?
> hmm, i might hit a technical misunderstanding of mine here:
> doesn't the VO have the only jobs submitter machine (WMS) for the
> respective VO? If so, the WMS can log directly the user DN and the
> associated job information that can lead to more detailed accounting.

Submission through WMS is just one of the possible supported mechanisms 
for job submission to CEs. Direct submission is also used by many VOs 
including WLCG. As to WMS, a VO can use a pool of WMS servers, so even 
if WMS were able to collect accounting data (which is not at the 
moment), the VO would still need a DB for aggregation.

>    So .. is it possible to send a job to a site with some VO credentials
> directly? well, that mean IMHO that EMI is deeply _broken_ from a
> security point of view!! a site should receive jobs ONLY from an
> authenticated submission server of the VO and no other! (and the UI part
> of job submission should connect only to this central(VO) submission
> mechanism)

Submission through WMS does not make the CE infrastructure more secure.
WMS submits to CEs by means of user-delegated credentials.

> Well, i am still not satisfied with this "centrally" and the submission
> mechanism should be fast repaired. The thing is that we are a small
> institute and we cannot afford any "potential" legal problems.

The user DN information is encrypted when transported to the central 
accounting DB. User-level accounting information is only made accessible 
to the user, and to the respective VO managers.
User data is treated confidentially by the DB administrators and used 
for the sole purpose of the provisioning of grid services (like many 
other organizations which handle private information).

Tiziana Ferrari
-- 
Tiziana Ferrari
EGI.eu Operations
0031 (0)6 3037.2691

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

March 2024
November 2023
June 2023
May 2023
April 2023
March 2023
February 2023
September 2022
June 2022
May 2022
April 2022
February 2022
December 2021
November 2021
October 2021
September 2021
July 2021
June 2021
May 2021
February 2021
January 2021
November 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
February 2018
January 2018
November 2017
October 2017
September 2017
July 2017
June 2017
May 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
2006
2005
2004
2003


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager