Ticket #235 (closed task: wontfix)

Opened 14 years ago

Last modified 13 years ago

[S] Security deployed on Superglue

Reported by: selatham Owned by: pjkersha
Priority: required Milestone: Replace Metadata Gateway
Component: security Version:
Keywords: Cc:


Deploy stable version of security on superglue. This can be used by DP's during testing.

Change History

comment:1 Changed 14 years ago by lawrence

  • Milestone changed from PreAlpha to PostAlpha_review

Not an alpha issue.

comment:2 Changed 14 years ago by pjkersha

  • Status changed from new to assigned

Delayed because Ingres client won't install on superglue.

Ingres client s/w is required so that the Attribute Authority can query user/roles info from the BADC db on chinook.

To date:

  • Andrew Harwood tried the open source download from Ingres site but this fails with 'su' errors
  • Phil tried but same errors - written to Ingres mailing list but no responses that would sort the problem out
  • Brian Coan has tried with alternative version of s/w but installation script hangs.
  • Brian tried again with CDs from distro from RAL Ingres contact - script hangs
  • Brian has asked RAL rep to query with Ingres and get specific CDs for Redhat Enterprise 4

comment:3 Changed 14 years ago by selatham

Just noticed that ingres is running on glue. So we must have got an appropriate download in the past. On glue running:-

ingres 2590 0.0 0.0 2844 856 ? S Jul05 0:13 /opt/CA/IngresII/ingres/bin/iigcn II ingres 2603 0.0 0.0 2876 1060 ? S Jul05 0:03 /opt/CA/IngresII/ingres/bin/iigcc II gcc ingres 3171 0.0 0.0 3724 660 ? S Jul05 0:02 /opt/CA/IngresII/ingres/bin/iigcd II gcd

comment:4 Changed 14 years ago by pjkersha

  • Milestone changed from PostAlpha_review to BETA

Brian Coan set up Ingres on superglue 19/09/06 but the Python Ingres plugin install fails.

At Meeting 'Discovery/Browse?/DX on superglue' 19/09/06 agreed to postpone installation until user database issues fully resolved. This may involve migration of user database from Ingres to another db vendor.

Barring the Attribute Authority link to the user database, the security installation is complete with Aplpha version in place. The Attribute Authority has a test stub in place of the link to the Ingres user db.

Moving this ticket to Beta milestone in line with possible migration of user db.

comment:5 Changed 14 years ago by pjkersha

  • 0.72 post-alpha is installed with a stub in place of the connection to the Ingres user database - left as so until the database issue is resolved ...
  • The above doesn't work with the version of Browse on superglue - leave this now as beta versions of security and Browse will superceed anyway.
  • What is likely timetable for move from Ingres?

comment:6 Changed 13 years ago by lawrence

  • Milestone changed from BETA to BETA+Security

comment:7 Changed 13 years ago by lawrence

NB, this is required by WSGI middleware.

comment:8 Changed 13 years ago by selatham

  • Milestone changed from PROD Step2 to Replace Metadata Gateway

If this was for testing, then shouldn't be on production machine. Note that Ingres not now required (BADC now uses postgres for userdb). Do we actually need to install security as part of the deployed NERC DDS stack?

comment:9 Changed 13 years ago by selatham

  • Status changed from assigned to closed
  • Resolution set to wontfix

We are not deploying security on the NERC-DDS. Should be on DP's browse services only.

Note: See TracTickets for help on using tickets.