Bug #15649

Issue #7186 Broke submission to AWS which also uses key_pair as auth_method

Added by Parag Mhashilkar almost 4 years ago. Updated over 3 years ago.

Parag Mhashilkar
Target version:
Start date:
Due date:
% Done:


Estimated time:
First Occurred:
Occurs In:
Duration: 69


2017-02-22 09:34:52,361] DEBUG: glideFactoryEntry:1006: Checking security credentials for client cmssrv279-fnal-gov_OSG_gWMSFrontend.fermilab
[2017-02-22 09:34:52,362] WARNING: glideFactoryEntry:1300: Client 'cmssrv279-fnal-gov_OSG_gWMSFrontend.fermilab' did not specify a Username in Key 742746 and the entry FNAL_HEPCLOUD_AWS_us-west-2a_m3.xlarge does not provide a default username in the gatekeeper string, skipping request

The AWS secret key / access key don't have a username in them the way they are stored,
there is just the 20 byte AWS access key and the 40 byte secret access key.

What should we do? I don't think we tested the AWS functionality after 3.3.1 was released before.

Steve Timm


#1 Updated by Parag Mhashilkar almost 4 years ago

  • Assignee set to Parag Mhashilkar
  • Target version set to v3_2_19
  • First Occurred set to v3_2_16

Following changes from Marco to ticket broke the AWS submission. AWS & BOSCO both use key_pair but the changes made do not distinguish appropriately.

—— COMMIT ——

This is an automated email from the git hooks/post-receive script.

marcom pushed a commit to branch v3/7186_2
in repository glideinwms.

commit 6ac16a2473cb890449ae2f6bf658b20d8706f9f2
Author: Marco Mambelli
Date: Mon Sep 12 17:05:28 2016 -0500

added remote_username credential attribute. If specified will replace username in user@host from entry when using key pair

#2 Updated by Parag Mhashilkar over 3 years ago

  • Status changed from New to Feedback
  • Assignee changed from Parag Mhashilkar to Marco Mambelli

#3 Updated by Steven Timm over 3 years ago

You are showing 3.2 version tags in the notes. We need the patch for 3.3 series.

Steve Timm

#4 Updated by Marco Mambelli over 3 years ago

  • Assignee changed from Marco Mambelli to Parag Mhashilkar

OK to merge

#5 Updated by Parag Mhashilkar over 3 years ago

  • Status changed from Feedback to Resolved

#6 Updated by Parag Mhashilkar over 3 years ago

  • Due date set to 05/02/2017

#7 Updated by Parag Mhashilkar over 3 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF