Page MenuHomePhabricator

Requesting access to Superset for jniren-ctr
Closed, ResolvedPublicRequest

Description

Username: jniren-ctr
Shell access: No
Purpose: Superset dashboard and Superset SQL lab
Group: nda
Contract end date: 2026-07-31
Contract contact: nnawaz AT WM.org

Original request:

Requestor provided information and prerequisites

Complete ALL items below as the individual person who is requesting access:

  • Wikimedia developer account username: jniren-ctr
  • Email address: jniren-ctr@wikimedia.org
  • SSH public key (must be a separate key from Wikimedia cloud SSH access):
  • Requested group membership: nda
  • Reason for access: Superset dashboard and Superset SQL lab
  • Name of approving party (manager for WMF/WMDE staff): @AAlikhan
  • Ensure you have signed the L3 Wikimedia Server Access Responsibilities document:
  • Please coordinate obtaining a comment of approval on this task from the approving party.

SRE Clinic Duty Confirmation Checklist for Access Requests

This checklist should be used on all access requests to ensure that all steps are covered, including expansion to existing access. Please double check the step has been completed before checking it off.

This section is to be confirmed and completed by a member of the SRE team.

[N/A] - User has signed the L3 Acknowledgement of Wikimedia Server Access Responsibilities Document.

  • - User has a valid NDA on file with WMF legal. (All WMF Staff/Contractor hiring are covered by NDA. Other users can be validated via the NDA tracking sheet)
  • - User has provided the following: developer account username, email address, and full reasoning for access (including what commands and/or tasks they expect to perform)

[N/A] - User has provided a public SSH key. This ssh key pair should only be used for WMF cluster access, and not shared with any other service (this includes not sharing with WMCS access, no shared keys.)
[N/A] - The provided SSH key has been confirmed out of band and is verified not being used in WMCS.

  • - access request (or expansion) has sign off of WMF sponsor/manager (sponsor for volunteers, manager for wmf staff)

[N/A] - access request (or expansion) has sign off of group approver indicated by the approval field in data.yaml

For additional details regarding access request requirements, please see https://wikitech.wikimedia.org/wiki/Requesting_shell_access

Details

Event Timeline

jcrespo added subscribers: KFrancis, jcrespo.

Hi, @soworu to add you to the NDA group, we will need 2 things: your currently stated end of contract date and contact for contract (It could be @AAlikhan).

And we will need @KFrancis to help you sign the actual NDA document, or confirm this was already done as part of your existing contract.

Once both things are done, we will add you to the analytics-privatedata-users group but without ssh production access, for web dashboard access only, which I belive it is what you want.

jcrespo triaged this task as High priority.Jul 16 2026, 6:42 AM

HI @jcrespo, as part of the Main Services Agreement I have signed it includes the below section on confidential information but I have not signed a separate NDA.

Please let me know if the below covers me or if I need to some something additional?

  1. CONFIDENTIAL INFORMATION

7.1 Agreement to Maintain Confidentiality Service Provider acknowledges that in the
course of providing the Services to WMF Service Provider will occupy a position of
trust and confidence. Service Provider shall not, except as may be required to
perform any of the duties hereunder for WMF’s sole benefit or as required by
applicable law, disclose to others or use, directly or indirectly, any Confidential
Information as defined herein and shall use discretion and good faith in disclosing
information other than Confidential Information.
7.2 Definition of Confidential Information. Confidential Information means the
following:
(a) strategic plans, materials, technical data, trade secrets, know-how and other
proprietary information of the WMF;
(b) any information about commitments of, or proposals by, WMF to third parties,
including without limitation the existence and terms of actual or potential
business relationships of WMF;
(c) personally identifiable information or financial information regarding WMF
donors, volunteers or community members of a Wikimedia Project;
(d) WMF financial, employee or contractor records or information; and
(e) anything specifically marked as “confidential” or, if disclosed orally or in
tangible form (such as a product sample) identified as “confidential”.
7.3 Exceptions to Confidential Information Confidential Information shall not include
information that:
(a) is or becomes publicly known through no wrongful or negligent act of the
Service Provider;
(b) was in Service Provider’s possession before disclosure by WMF, as
evidenced by Service Provider’s written records, and was not initially obtained
by Service Provider subject to an expectation of confidentiality;
(c) was rightfully acquired by Service Provider after disclosure by WMF from a
third party who was lawfully in possession of the information and was under
no obligation to WMF to maintain its confidentiality;
(d) is independently developed by Service Provider’s employees or agents who
have not had access to the Confidential Information;
(e) Service Provider is required to disclose in accordance with a judicial order or
other legal requirement, provided that Service Provider shall promptly notify
WMF prior to disclosure to the extent permitted by law, reasonably cooperate
with any efforts by WMF to challenge a disclosure requirement and comply
with any protective order imposed on disclosure; or
(f) is specifically pre-approved for release by the WMF in writing.
7.4 Ownership of Confidential Information; Disposal. All Confidential Information
shall be solely and absolutely vested in and owned by WMF or its licensors or its
licensors, and the Service Provider shall not have or claim any right, title or interest
therein. Upon WMF request, Service Provider shall promptly return or destroy all
documents, samples or other materials embodying Confidential Information, shall
retain no copies thereof, and shall certify in writing that its return or destruction has
been accomplished
7.5 Data Security. Service Provider shall notify WMF immediately (i.e. within twenty-four
(24) hours) upon a data security breach or any reasonable suspicion thereof or any
other unauthorized access to or disclosure, loss or destruction of Confidential
Information or unauthorized access to WMF information technology (each, a Security
Event), and (1) promptly investigate, and (2) assist and fully cooperate with WMF with
regard to any remedial measures and any notices to affected individuals, organizations
or government agencies that WMF determines, in its sole discretion, may be required
by applicable laws, rules or WMF agreement or policies, in each case (1) and (2) at
Service Provider's sole expense, as requested by WMF and/or as required under
applicable law. Service Provider shall also be responsible for any acts or omissions of its employees and Assistants relating to any Security Event and shall cause such
employees and Assistants to abide by the foregoing notification obligations.

I am not a lawyer, so @KFrancis will confirm.

Hi all, as Jonathan Niren is currently a contractor with the WMF, an NDA is not needed. It's covered under the contractor contract. Thank you!

Thank you for confirming. Based on that, we should grant the wmf group, not nda, which is intended for volunteers with a separate NDA. @Jniren-ctr Requesting the wmf group has to be done outside of phabricator, with this procedure: https://wikitech.wikimedia.org/wiki/SRE/LDAP/Groups/Request_access#Using_the_Wikimedia_Identity_Management_System

The request is still pending two data points: a "Contract end date" and "Contract contact" as mentioned above, to be confirmed by the manager in charge.

Thanks @jcrespo - I have requested that permission for wmf group.

Re other two points:
Contract end date - Its currently 31st July 2026 but an extension to 30 September 20206 will be finalised in the next couple of working days - let me know if we need to wait for that?
Contract contact - is this the name of the WMF Contact named on the contract? Thats Nazneen Nawaz

end date - Whatever is true at the moment is ok, we will not remove access without asking first as it is common there are extensions, which is why we ask for a:
Contract contact - It is the name of the authoritative person @ wmf that we will contact if the date of the contract passes to check if it has been extended. Normally it is the person you report to (e.g. manager) but anyone that will know your contract status will be ok.

@jcrespo great. Then its 31st July and Nazneen Nawaz. Thank you.

@Fabfur handing this to you, this is ready for the group and LDAP data.yaml patch as soon as the WMF group is approved by IF https://ldap.toolforge.org/user/jniren-ctr

Change #1311852 had a related patch set uploaded (by Fabfur; author: Fabfur):

[operations/puppet@production] admin: record ldap access for jniren-ctr

https://gerrit.wikimedia.org/r/1311852

Hi and welcome @Jniren-ctr, please also connect your SUL WMF account to your Phabricator profile via https://phabricator.wikimedia.org/settings/panel/external/. This makes verification of numerous access requests etc easier and also generally improves transparency. Thanks!

@Jniren-ctr merging the change today and this should be completed

Change #1311852 merged by Fabfur:

[operations/puppet@production] admin: record ldap access for jniren-ctr

https://gerrit.wikimedia.org/r/1311852

HI @Aklapper - think thats done now

@Jniren-ctr: Hi, unfortunately a self-created account "Jonnyniren" was attached, but not the WMF created account "JNiren-WMF", so this is misleading now.

Hi @Aklapper apologies - Im still getting to grips with these accounts and identities. I have unlinked the jonnyniren account but now dont see any option to link a different account. If I try again, it only shows me the option to add an external Mediawiki account and defaults to the jonnyniren account. Please advise? Thanks

I think you first need to log into mediawiki.org with your WMF provided SUL account, after logging out of mediawiki.org with that personal account

@Aklapper thank you. Yes I believe that has worked. Correct account now linked.

Fabfur claimed this task.

I'm going to close this ticket, please reopen if needed