authinfo incompatibility with saspy module

Abierto
  • ¿Algo no está bien?
#178 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
35/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Estancado
Stack tecnológico
python
Área
authentication

Línea de trabajo

Comience en utils/authinfo.py:191 e inspeccione cómo el parser divide los registros de .authinfo. Reproduzca el problema con las entradas denominadas IOM_Linux_SASGrid y default que se muestran en el informe y, después, verifique que las configuraciones denominadas ya no interrumpan el análisis y que el registro default se seleccione correctamente.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

I'm using both saspy [for sas_kernel/jupyter as well as some of our 9.4 systems and SAS Grid], as well as SWAT for working directly with CAS. I spent quite a while trying to debug a connection issue with SWAT that turned out to be due to how my .authinfo was written.

What I had originally looked like this:

IOM_Linux_SASGrid user not_my_real_user password not_my_real_password
default user not_my_real_user password not_my_real_password

SWAT kept having authentication problems, because the syntax with the named config line doesn't work with the parser process in utils/authinfo.py:191 , where it splits on "host|machine|default".

The SASPy documentation is here: https://sassoftware.github.io/saspy/configuration.html#iom , this is the line about "authkey" that's specced thus, that is the line causing the problem:

authkey user omr_user_id password omr_user_password

My workaround was to flip the lines:

default user not_my_real_user password not_my_real_password
IOM_Linux_SASGrid user not_my_real_user password not_my_real_password

And now the "default" one is correctly picked up, [and the rest of the "defs" variable is nonsensical from the perspective of the rest of the parsing code, but it doesn't matter because it doesn't play because default already got returned]

Because the named configs don't make sense with SWAT's configuration, I would suggest the shortest fix that is to split on line breaks first, then split the rest, the way you do now. That way, named configs will be functionally ignored but won't break subsequent records.

Lenguaje dominante
Python
Estrellas
159
Forks
66
Sin PR fusionados en 30 d

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de sassoftware/python-swat

Todos los issues de sassoftware/python-swat

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.