|
96.
|
|
|
Direct import of auth plugin %(name)r is deprecated as of Liberty in favor of its entrypoint from %(namespace)r and may be removed in N.
|
|
|
|
La importación directa del plug-in de autorización %(name)r está en desuso a partir de Liberty, sustituyéndose por su punto de entrada desde %(namespace)r y puede que se elimine en N.
|
|
Translated by
Eugènia Torrella
|
|
Reviewed by
Paco Molinero
|
|
|
|
Located in
keystone/auth/controllers.py:60
|
|
97.
|
|
|
Unable to reconcile identity attribute %(attribute)s as it has conflicting values %(new)s and %(old)s
|
|
|
|
No se puede reconciliar el atributo de identidad %(attribute)s porque tiene los siguientes valores en conflicto: %(new)s y %(old)s
|
|
Translated by
Eugènia Torrella
|
|
Reviewed by
Adolfo Jayme Barrientos
|
In upstream: |
|
No se puede reconciliar el atributo de identidad %(attribute)s porque tiene los valores en conflicto %(new)s y %(old)s
|
|
|
Suggested by
openstackjenkins
|
|
|
|
Located in
keystone/auth/controllers.py:121
|
|
98.
|
|
|
Domain name cannot contain reserved characters.
|
|
|
|
El nombre de dominio no puede contener caracteres reservados.
|
|
Translated by
Eugènia Torrella
|
|
|
|
Located in
keystone/auth/controllers.py:182
|
|
99.
|
|
|
Project name cannot contain reserved characters.
|
|
|
|
El nombre de proyecto no puede contener caracteres reservados.
|
|
Translated by
Eugènia Torrella
|
|
|
|
Located in
keystone/auth/controllers.py:205
|
|
100.
|
|
|
Scoping to both domain and project is not allowed
|
|
|
|
No se permite definir el ámbito tanto a dominio como a proyecto
|
|
Translated by
Eugènia Torrella
|
|
Reviewed by
Adolfo Jayme Barrientos
|
In upstream: |
|
El ámbito para dominio y proyecto no está permitido
|
|
|
Suggested by
Ying Chun Guo
|
|
|
|
Located in
keystone/auth/controllers.py:355 keystone/middleware/auth.py:130
|
|
101.
|
|
|
Scoping to both domain and trust is not allowed
|
|
|
|
No se permite definir el ámbito tanto a dominio como a confianza
|
|
Translated by
Eugènia Torrella
|
|
Reviewed by
Adolfo Jayme Barrientos
|
In upstream: |
|
El ámbito para dominio y confianza no está permitido
|
|
|
Suggested by
Ying Chun Guo
|
|
|
|
Located in
keystone/auth/controllers.py:358
|
|
102.
|
|
|
Scoping to both project and trust is not allowed
|
|
|
|
No se permite definir el ámbito tanto a proyecto como a confianza
|
|
Translated by
Eugènia Torrella
|
|
Reviewed by
Adolfo Jayme Barrientos
|
In upstream: |
|
El ámbito para proyecto y confianza no está permitido
|
|
|
Suggested by
Ying Chun Guo
|
|
|
|
Located in
keystone/auth/controllers.py:361
|
|
103.
|
|
|
User not found
|
|
|
|
Usuario no encontrado
|
|
Translated by
Ying Chun Guo
|
|
|
|
Located in
keystone/auth/controllers.py:530
|
|
104.
|
|
|
A project-scoped token is required to produce a service catalog.
|
|
|
|
Se necesita un token con ámbito de proyecto para producir un catálogo de servicio.
|
|
Translated by
Eugènia Torrella
|
|
Reviewed by
Paco Molinero
|
In upstream: |
|
Se necesita una señal con ámbito de proyecto para producir un catálogo de servicio.
|
|
|
Suggested by
openstackjenkins
|
|
|
|
Located in
keystone/auth/controllers.py:644
|
|
105.
|
|
|
No authenticated user
|
|
|
|
No hay ningún usuario autenticado
|
|
Translated by
Eugènia Torrella
|
|
Reviewed by
Adolfo Jayme Barrientos
|
In upstream: |
|
Ningún usuario autenticado
|
|
|
Suggested by
Paco Molinero
|
|
|
|
Located in
keystone/auth/plugins/external.py:42
|