MOSRS authentication : ERROR checking password

Atmosphere Unified Model
,
1

Hi all.

My MOSRS account is now re-activated and I’m getting set up on gadi for the first time (previously I used MOSRS on raijin).

I’ve added the following to ~/.subversion/servers

[groups]
metofficesharedrepos = code*.metoffice.gov.uk

[metofficesharedrepos]
username = XXXXXX # set to your username
store-plaintext-passwords = no

I’ve follow the steps described here: Setup — Aus2200 Training

module purge
module use /g/data/hr22/modulefiles
module load pbs cylc7
mosrs-auth

I’ve followed notes here : https://code.metoffice.gov.uk/trac/home/wiki/AuthenticationCaching

 $ grep  password-stores ~/.subversion/config 
# password-stores = gpg-agent,gnome-keyring,kwallet
# password-stores =

The following generates no output (which is correct):

$ rose config --print-conf -f ~/.subversion/config auth password-stores

But authentication fails with the following error:

$ mosrs-auth
MOSRS username XXXXX # set to your username - change in ~/.subversion/servers
Current project dx2
Checking stored password...
ERROR checking password
HTTP Error 401: Unauthorized

The password I’ve entered is the same to access code.metoffice.gov.uk.

I have membership to ki32, and ki32_mosrs.

Cheers,

Paul

2

Hi Paul,

Just in case this helps, the mosrs-auth is only required when checking out or committing a rose/cylc suite, so in general the authentication in not required all the time.

For research purposes it seems ok to just enter the name and password when running the mosrs-auth with no authentication caching.

That may not suite your purposes though … but may start you running if you are currently feeling stuck.

Best regards,

Chermelle

3

Thanks Chermelle. Checkout of rose suites was standard BoM practise, I’m not familiar with other methods to obtaining a rose suite. What are they?

How can you run moss-auth with no authentication caching?

Note my MOSRS password works as I can execute the following:

$ fcm info https://code.metoffice.gov.uk/svn/glosea/main/trunk/rose-stem/bin/scitool-run@5989
Authentication realm: <https://code.metoffice.gov.uk:443> Met Office Code
Password for 'XXXXXX': ********************

Path: scitool-run
Name: scitool-run
URL: https://code.metoffice.gov.uk/svn/glosea/main/trunk/rose-stem/bin/scitool-run
Relative URL: ^/main/trunk/rose-stem/bin/scitool-run
Repository Root: https://code.metoffice.gov.uk/svn/glosea
Repository UUID: e14a8879-62c6-4f65-aad6-6a06efb4d672
Revision: 5989
Node Kind: file
Last Changed Author: joemancell
Last Changed Rev: 5989
Last Changed Date: 2023-06-20 19:35:03 +1000 (Tue, 20 Jun 2023)
5

Try the --force flag to make mosrs-auth request a password

6

Hi Scott. I tried --force yesterday to no avail.

I’m going to look into the python calls within the mosrs-auth script and try to get a minimum working example up and running in python.

7

I assume you’re putting your actual username in that file and are obscuring it for security, which is good practice.

On that assumption it is worth checking the whole ~/.subversion/servers file. I had an error when I added something like that to the end, but there was already a [groups] defined, so it threw an error to that effect that was swallowed by the mosrs-auth script.

8

Ok I solved it.

I created a python test script to see what the inputs mosrs-auth was passing to the urllib request.

The actual value of user inside the python script is

In [3]: user
Out[3]: 'myusername # set to your username'

I assumed that a bash comment would be ignored by the script. Not so - indeed the stdout from mosrs-auth was

MOSRS username XXXXX # set to your username - change in ~/.subversion/servers
Current project dx2

So all I did was change my ~/.subversion/config entry from

username = xxxxxxxx # set to your username

to

username = xxxxxxxx

And authentication works.

Onwards and upwards.

1 Like