Skip to Content.

cat-users - [[cat-users]] Linking new organisations to eduroam database

cat-users AT lists.geant.org

Subject: The mailing list for users of the eduroam Configuration Assistant Tool (CAT)

List archive


[[cat-users]] Linking new organisations to eduroam database


Chronological Thread 
  • From: Nik Mitev <nik.mitev AT jisc.ac.uk>
  • To: cat-users AT lists.geant.org
  • Subject: [[cat-users]] Linking new organisations to eduroam database
  • Date: Tue, 23 Jan 2018 09:17:16 +0000
  • Authentication-results: prod-mail.geant.net (amavisd-new); dkim=pass (1024-bit key) header.d=jisc.ac.uk
  • Authentication-results: spf=none (sender IP is ) smtp.mailfrom=Nik.Mitev AT jisc.ac.uk;
  • Spamdiagnosticmetadata: NSPM
  • Spamdiagnosticoutput: 1:99

Hi,

When new eduroam members request CAT access, they can join but their CAT
instance is not linked to the eduroam database as they have not yet
completed their eduroam deployment and are not listed.

While they are in this state, is there any technical (as opposed to
policy) limitation to how they can use CAT?

Once they have claimed their compliance and have been listed in the
eduroam database, and IF there is a delay in creating the link in CAT...
in the admin manual it says this can lead to the two databases getting
out of sync. It is of course not a good state to be in, but what are the
practical consequences - what can/will break?
Also, if an out of sync instance is then linked, which database takes
precedence when syncing (and overwrites the other)?

I am thinking about giving people easier access to CAT, so they can work
on it alongside the rest of their deployment, but not sure I fully
understand the potential downsides - any help appreciated.

Thanks,
Nik
--
Nik Mitev
eduroam UK Technical Support, Jisc
www.eduroam.uk

When replying to this e-mail is it essential to preserve the
(Ref:IN:XXXXXXXX) text in the subject line and to always use 'Reply All'

Attachment: signature.asc
Description: OpenPGP digital signature




Archive powered by MHonArc 2.6.19.

Top of Page