Hello,

We are probably not using the same exact version and although my main issue 
proved to be different at the end, at some point during my authentication 
issues...marathon I did get a similar message and I ended up setting the value 
to "umls_api_key" for umls user and the  umls pwd =  API_KEY wherever I could 
find relevant references in the source code.

Again it may probably not be applicable in your case and even for my case, I 
had to take other steps eventually to resolve my auth issues, but these 
settings made or at least appeared to make that message go away for me so 
thought I'd mention it just in case...

Kind Regards,

Eugenia Monogyiou | NTT Data UK
Consulting & IT Solutions Ltd. 1 Royal Exchange, London EC3V 3DG

Mob: +44 (0)7971623683 Email: eugenia.monogy...@nttdata.com


-----Original Message-----
From: Peter Abramowitsch <pabramowit...@gmail.com>
Sent: 10 February 2021 19:20
To: dev@ctakes.apache.org
Subject: Re: authentication issue?

Hi Greg

401 means either not authenticated or there's a problem at the UMLS end - which 
does happen every now and then.  I've already told their guy about
it,   But at this very instant 19:18 GMT, it is working

10 Feb 2021 20:18:43  INFO UmlsUserApprover - Checking UMLS Account at
https://utslogin.nlm.nih.gov/cas/v1/api-key:
......10 Feb 2021 20:18:45  INFO UmlsUserApprover -   UMLS Account has been
validated


Peter

On Wed, Feb 10, 2021 at 7:12 PM Greg Silverman <g...@umn.edu.invalid> wrote:

> This had been working (4.0.0.1), but now am getting the following error:
>
> 10 Feb 2021 18:03:40  INFO SentenceDetector - Sentence detector model file:
> org/apache/ctakes/core/sentdetect/sd-med-model.zip
> 10 Feb 2021 18:03:40  INFO TokenizerAnnotatorPTB - Initializing
> org.apache.ctakes.core.ae.TokenizerAnnotatorPTB
> 10 Feb 2021 18:03:40  INFO ContextDependentTokenizerAnnotator - Finite
> state machines loaded.
> 10 Feb 2021 18:03:40  INFO POSTagger - POS tagger model file:
> org/apache/ctakes/postagger/models/mayo-pos.zip
> 10 Feb 2021 18:03:41  INFO Chunker - Chunker model file:
> org/apache/ctakes/chunker/models/chunker-model.zip
> 10 Feb 2021 18:03:42  INFO AbstractJCasTermAnnotator - Using
> dictionary lookup window type:
> org.apache.ctakes.typesystem.type.textspan.Sentence
> 10 Feb 2021 18:03:42  INFO AbstractJCasTermAnnotator - Exclusion
> tagset
> loaded: CC CD DT EX IN LS MD PDT POS PP PP$ PRP PRP$ RP TO VB VBD VBG
> VBN VBP VBZ WDT WP WPS WRB
> 10 Feb 2021 18:03:42  INFO AbstractJCasTermAnnotator - Using minimum
> term text span: 3
> 10 Feb 2021 18:03:42  INFO AbstractJCasTermAnnotator - Using
> Dictionary
> Descriptor: org/apache/ctakes/dictionary/lookup/fast/sno_rx_16ab.xml
> 10 Feb 2021 18:03:42  INFO DictionaryDescriptorParser - Parsing
> dictionary
> specifications:
> 10 Feb 2021 18:03:42 ERROR UmlsUserApprover -   umlsUser CHANGE_ME not
> allowed.  It is a placeholder reminder.
> 10 Feb 2021 18:03:42 ERROR UmlsUserApprover -   umlsPass CHANGE_ME not
> allowed.  It is a placeholder reminder.
> 10 Feb 2021 18:03:42  INFO UmlsUserApprover - Checking UMLS Account at
> https://utslogin.nlm.nih.gov/cas/v1/api-key:
> ..
> 10 Feb 2021 18:03:43 ERROR UmlsUserApprover - Server returned HTTP
> response
> code: 401 for URL: https://utslogin.nlm.nih.gov/cas/v1/api-key
> 10 Feb 2021 18:03:43 ERROR PiperFileRunner - Initialization of
> annotator class 
> "org.apache.ctakes.dictionary.lookup2.ae.DefaultJCasTermAnnotator"
> failed.  (Descriptor: <unknown>)
> /data/ctakes_out /usr/share/ctakes
>
>
>
> --
> Greg M. Silverman
> Senior Systems Developer
> NLP/IE <https://healthinformatics.umn.edu/research/nlpie-group>
> Department of Surgery
> University of Minnesota
> g...@umn.edu
>
Disclaimer: This email and any attachments are sent in strictest confidence for 
the sole use of the addressee and may contain legally privileged, confidential, 
and proprietary data. If you are not the intended recipient, please advise the 
sender by replying promptly to this email and then delete and destroy this 
email and any attachments without any further use, copying or forwarding.

Reply via email to