Hi fellow translators!

FreeIPA project changed component list. Components for older branches were removed, and now only the same master component and the new stable-release component which will be updated on new releases.

Translation status

9,824 Strings
59%
Browse Translate
118,459 Words
33%
814,325 Characters
32%

Strings status

Strings Words Characters
9,824 118,459 814,325
All strings Browse Translate Zen
6,105 48,080 324,242
Translated strings Browse Translate Zen
3,719 70,379 490,083
Unfinished strings Browse Translate Zen
1,054 44,853 315,923
Untranslated strings Browse Translate Zen
2,665 25,526 174,160
Strings marked for edit Browse Translate Zen
545 10,690 74,254
Strings with suggestions Browse Translate Zen
3,213 59,830 416,690
Unfinished strings without suggestions Browse Translate Zen
799 20,143 141,282
Strings with any failing checks Browse Translate Zen
220 8,549 59,740
Translated strings with any failing checks Browse Translate Zen
7 36 257
Translated strings with dismissed checks Browse Translate Zen
36 61 452
Failing check: Unchanged translation Browse Translate Zen
30 232 1,633
Failing check: Starting newline Browse Translate Zen
57 443 3,045
Failing check: Trailing newline Browse Translate Zen
36 144 1,022
Failing check: Starting spaces Browse Translate Zen
83 1,099 7,370
Failing check: Trailing space Browse Translate Zen
17 514 3,265
Failing check: Double space Browse Translate Zen
281 1,842 12,292
Failing check: Mismatched full stop Browse Translate Zen
15 48 328
Failing check: Mismatched colon Browse Translate Zen
4 16 94
Failing check: Mismatched question mark Browse Translate Zen
4 16 94
Failing check: Mismatched exclamation mark Browse Translate Zen
131 662 4,589
Failing check: Multiple capitals Browse Translate Zen
102 584 3,787
Failing check: Python format Browse Translate Zen
113 791 5,979
Failing check: Python brace format Browse Translate Zen
2 18 116
Failing check: C format Browse Translate Zen
2 12 96
Failing check: Same plurals Browse Translate Zen
6 146 1,200
Failing check: Inconsistent Browse Translate Zen
4 6 34
Failing check: Reused translation Browse Translate Zen
176 16,684 117,167
Failing check: Mismatching line breaks Browse Translate Zen
2 56 516
Failing check: XML markup Browse Translate Zen
6 170 1,426
Failing check: Chars around XML tags Browse Translate Zen
Component Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
Glossary freeipa GPL-3.0-or-later
master GPL-3.0-or-later 62% 1,826 34,797 242,344 516 386 455
stable-release GPL-3.0-only 61% 1,893 35,582 247,739 538 413 90

Summary

Project website www.freeipa.org
Instructions for translators

Mailing list for translators: trans@lists.fedoraproject.org
Project maintainers2 User avatar abbraUser avatar cheimes
Language Spanish
Language code es
Text direction Left to right
Case sensitivity Case-sensitive
Number of speakers 507,599,381
09/10/2026

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 9,824 118,459 814,325
Translated 62% 6,105 40% 48,080 39% 324,242
Needs editing 27% 2,665 21% 25,526 21% 174,160
Read-only 0% 0 0% 0 0% 0
Failing checks 8% 799 17% 20,143 17% 141,282
Strings with suggestions 5% 545 9% 10,690 9% 74,254
Untranslated strings 10% 1,054 37% 44,853 38% 315,923
Last 12 months Previous

Activity in last 12 months

0 changes 883 changes 1 change 73 changes 0 changes 181 changes 0 changes 218 changes 0 changes 0 changes 0 changes 0 changes 0 changes 1 change 4 changes 0 changes 0 changes 0 changes 8 changes 35 changes 34 changes 9,824 changes 0 changes 2,574 changes
SepOctNovDecJanFebMarAprMayJunJulAug

Quick numbers

118 k
Hosted words
9,824
Hosted strings
62%
Translated
9
Contributors
and previous 30 days

Trends of last 30 days

+1%
Hosted words
—
+1%
Hosted strings
—
−1%
Translated
—
+100%
Contributors
—
User avatar webhook:github

Changes committed
Changes committed 08/20/2026
User avatar None

Resource updated
The “po/es.po” file was changed. 08/20/2026
User avatar None

String updated in the repository

Topology

Management of a replication topology at domain level 1.

IPA server's data is stored in LDAP server in two suffixes:
* domain suffix, e.g., 'dc=example,dc=com', contains all domain related data
* ca suffix, 'o=ipaca', is present only on server with CA installed. It
contains data for Certificate Server component

Data stored on IPA servers is replicated to other IPA servers. The way it is
replicated is defined by replication agreements. Replication agreements needs
to be set for both suffixes separately. On domain level 0 they are managed
using ipa-replica-manage and ipa-csreplica-manage tools. With domain level 1
they are managed centrally using `ipa topology*` commands.

Agreements are represented by topology segments. By default topology segment
represents 2 replication agreements - one for each direction, e.g., A to B and
B to A. Creation of unidirectional segments is not allowed.

To verify that no server is disconnected in the topology of the given suffix,
use:
ipa topologysuffix-verify $suffix


Examples:
Find all IPA servers:
ipa server-find

Find all suffixes:
ipa topologysuffix-find

Add topology segment to 'domain' suffix:
ipa topologysegment-add domain --left IPA_SERVER_A --right IPA_SERVER_B

Add topology segment to 'ca' suffix:
ipa topologysegment-add ca --left IPA_SERVER_A --right IPA_SERVER_B

List all topology segments in 'domain' suffix:
ipa topologysegment-find domain

List all topology segments in 'ca' suffix:
ipa topologysegment-find ca

Delete topology segment in 'domain' suffix:
ipa topologysegment-del domain segment_name

Delete topology segment in 'ca' suffix:
ipa topologysegment-del ca segment_name

Verify topology of 'domain' suffix:
ipa topologysuffix-verify domain

Verify topology of 'ca' suffix:
ipa topologysuffix-verify ca
 
08/20/2026
User avatar None

String updated in the repository

ID ranges

Manage ID ranges used to map Posix IDs to SIDs and back.

There are two type of ID ranges which are both handled by this utility:

- the ID ranges of the local domain
- the ID ranges of trusted remote domains

Both types have the following attributes in common:

- base-id: the first ID of the Posix ID range
- range-size: the size of the range

With those two attributes a range object can reserve the Posix IDs starting
with base-id up to but not including base-id+range-size exclusively.

Additionally an ID range of the local domain may set
- rid-base: the first RID(*) of the corresponding RID range
- secondary-rid-base: first RID of the secondary RID range

and an ID range of a trusted domain must set
- rid-base: the first RID of the corresponding RID range
- sid: domain SID of the trusted domain



EXAMPLE: Add a new ID range for a trusted domain

Since there might be more than one trusted domain the domain SID must be given
while creating the ID range.

ipa idrange-add --base-id=1200000 --range-size=200000 --rid-base=0 --dom-sid=S-1-5-21-123-456-789 trusted_dom_range

This ID range is then used by the IPA server and the SSSD IPA provider to
assign Posix UIDs to users from the trusted domain.

If e.g. a range for a trusted domain is configured with the following values:
base-id = 1200000
range-size = 200000
rid-base = 0
the RIDs 0 to 199999 are mapped to the Posix ID from 1200000 to 13999999. So
RID 1000 <-> Posix ID 1201000



EXAMPLE: Add a new ID range for the local domain

To create an ID range for the local domain it is not necessary to specify a
domain SID. But since it is possible that a user and a group can have the same
value as Posix ID a second RID interval is needed to handle conflicts.

ipa idrange-add --base-id=1200000 --range-size=200000 --rid-base=1000 --secondary-rid-base=1000000 local_range

The data from the ID ranges of the local domain are used by the IPA server
internally to assign SIDs to IPA users and groups. The SID will then be stored
in the user or group objects.

If e.g. the ID range for the local domain is configured with the values from
the example above then a new user with the UID 1200007 will get the RID 1007.
If this RID is already used by a group the RID will be 1000007. This can only
happen if a user or a group object was created with a fixed ID because the
automatic assignment will not assign the same ID twice. Since there are only
users and groups sharing the same ID namespace it is sufficient to have only
one fallback range to handle conflicts.

To find the Posix ID for a given RID from the local domain it has to be
checked first if the RID falls in the primary or secondary RID range and
the rid-base or the secondary-rid-base has to be subtracted, respectively,
and the base-id has to be added to get the Posix ID.

Typically the creation of ID ranges happens behind the scenes and this CLI
must not be used at all. The ID range for the local domain will be created
during installation or upgrade from an older version. The ID range for a
trusted domain will be created together with the trust by 'ipa trust-add ...'.

USE CASES:

Add an ID range from a transitively trusted domain

If the trusted domain (A) trusts another domain (B) as well and this trust
is transitive 'ipa trust-add domain-A' will only create a range for
domain A. The ID range for domain B must be added manually.

Add an additional ID range for the local domain

If the ID range of the local domain is exhausted, i.e. no new IDs can be
assigned to Posix users or groups by the DNA plugin, a new range has to be
created to allow new users and groups to be added. (Currently there is no
connection between this range CLI and the DNA plugin, but a future version
might be able to modify the configuration of the DNS plugin as well)

In general it is not necessary to modify or delete ID ranges. If there is no
other way to achieve a certain configuration than to modify or delete an ID
range it should be done with great care. Because UIDs are stored in the file
system and are used for access control it might be possible that users are
allowed to access files of other users if an ID range got deleted and reused
for a different domain.

(*) The RID is typically the last integer of a user or group SID which follows
the domain SID. E.g. if the domain SID is S-1-5-21-123-456-789 and a user from
this domain has the SID S-1-5-21-123-456-789-1010 then 1010 is the RID of the
user. RIDs are unique in a domain, 32bit values and are used for users and
groups.

WARNING:

DNA plugin in 389-ds will allocate IDs based on the ranges configured for the
local domain. Currently the DNA plugin *cannot* be reconfigured itself based
on the local ranges set via this family of commands.

Manual configuration change has to be done in the DNA plugin configuration for
the new local range. Specifically, The dnaNextRange attribute of 'cn=Posix
IDs,cn=Distributed Numeric Assignment Plugin,cn=plugins,cn=config' has to be
modified to match the new range.

#Id gamas

Dirigen #ID gamas utilizaron a mapa Posix IDs a SIDs y atrás.

Hay dos tipo de ID varía cuáles son ambos manejados por esta utilidad:

- las #ID gamas del ámbito local
- las #ID gamas de los ámbitos remotos confiados en

Tanto los tipos tienen los atributos siguientes en común:

- base-id: el primer ID del Posix ID gama
- gama-medida: la medida de la gama

Con aquellos dos atributos un objeto de gama puede reservar el Posix IDs empezando
con base-id hasta pero no incluyendo base-id+gama-medida exclusivamente.

Además una ID gama del ámbito local puede poner
- librado-base: el primer LIBRADO() de la gama LIBRADA correspondiente
- secundario-librado-base: primero LIBRADO de la gama LIBRADA secundaria

y una ID gama de un ámbito confiado en tiene que poner
- librado-base: el primer LIBRADO de la gama LIBRADA correspondiente
- sid: ámbito SID del EJEMPLO de



ámbito confiado en: Añadir un nuevo ID gama para un ámbito confiado en

Desde entonces allí podría ser más de uno ámbito confiado en el ámbito SID tiene que ser dado
mientras creando la ID gama.

ipa idrange-Añadir --base-id=1200000 --gama-medida=200000 --librado-base=0 --dom-sid=S-1-5-21-123-456-789 confió en_dom_variar

Esta ID gama es entonces utilizada por el IPA servidor y el SSSD IPA proveedor para
asignar Posix UIDs a usuarios del ámbito confiado en.

Si p. ej. una gama para un ámbito confiado en está configurada con los valores siguientes:
base-id = 1200000
gama-medida = 200000
librado-base = 0
el Libra 0 a 199999 es mapped al Posix ID de 1200000 a 13999999. Tan
LIBRADO 1000 <-> Posix ID 1201000



EJEMPLO: Añadir un nuevo ID gama para el ámbito local

para crear una ID gama para el ámbito local no es necesario de especificar un
ámbito SID. Pero desde entonces es posible que un usuario y un grupo pueden tener el mismo
valor como Posix ID un segundo intervalo LIBRADO está necesitado para manejar conflictos.

ipa idrange-Añadir --base-id=1200000 --gama-medida=200000 --librado-base=1000 --secundario-librado-base=1000000 gama_local

El dato de las #ID gamas del ámbito local están utilizadas por el IPA servidor
internamente para asignar SIDs a IPA usuarios y grupos. El SID entonces será almacenado
en el usuario u objetos de grupo.

Si p. ej. la ID gama para el ámbito local está configurada con los valores del
ejemplo encima entonces un usuario nuevo con el UID 1200007 cogerá el LIBRADO 1007.
Si esto LIBRA es ya utilizado por un grupo el LIBRADO será 1000007. Esto sólo puede
pasar si un usuario o un objeto de grupo estuvo creado con un fijo ID porque la
tarea automática no asignará el mismo ID dos veces. Desde entonces hay usuarios
únicos y agrupa compartir el mismo ID namespace es suficiente de tener sólo
uno fallback gama para manejar conflictos.

Para encontrar el Posix ID para un dado LIBRADO del ámbito local tiene que ser
comprobado primero si el LIBRAR caídas en el primarios o gama LIBRADA secundaria y
el librado-base o el secundario-librado-la base tiene que ser restada, respectivamente,
y la base-id tiene que ser añadido para coger el Posix ID.

Típicamente la creación de #ID gamas pasa detrás de las escenas y esto CLI
no tiene que ser utilizado en absoluto. La ID gama para el ámbito local será creada
durante instalación o upgrade de una versión más vieja. La ID gama para un
ámbito confiado en será creada junto con la confianza por 'ipa confianza-añadir ...'.

CASOS de uso:

Añadir una ID gama de un transitively ámbito confiado en

Si el ámbito confiado en (Un) confía en otro ámbito (B) también y esta confianza
es transitive 'ipa confianza-añadir ámbito-Un' sólo creará una gama para
ámbito Un. La ID gama para ámbito B tiene que ser añadido manualmente.

Añadir un adicional ID gama para el ámbito local

Si la ID gama del ámbito local está agotada, i.e. ningún nuevo IDs puede ser
asignado a Posix usuarios o grupos por el ADN plugin, una gama nueva tiene que ser
creada para dejar grupos y usuarios nuevos para ser añadidos. (Actualmente no hay ninguna
conexión entre esta gama CLI y el ADN plugin, pero una versión futura
podría ser capaz de modificar la configuración del DNS plugin también)

En general no es necesario de modificar o eliminar #ID gamas. Si hay no
otra manera de conseguir una configuración segura que para modificar o eliminar una ID
gama tendría que ser hecho con cuidado sumo. Porque UIDs está almacenado en el sistema
de lima y está utilizado para el acceso lo controla podría ser posible que los usuarios están
dejados para acceder limas de otros usuarios si una ID gama cogió eliminada y reused
para un ámbito diferente.

() El LIBRADO es típicamente el último entero de un usuario o grupo SID cuál sigue
el ámbito SID. P. ej. si el ámbito SID es S-1-5-21-123-456-789 y un usuario de
este ámbito tiene el SID S-1-5-21-123-456-789-1010 entonces 1010 es el LIBRADO del
usuario. Libra es único en un ámbito, 32mordió valores y está utilizado para usuarios y
grupos.

Aviso:

ADN plugin en 389-ds destinará IDs basado en las gamas configuraron para el
ámbito local. Actualmente el ADN plugin no puede* ser reconfigured él basado
en las gamas locales puestas vía esta familia de órdenes.

Cambio de configuración manual tiene que ser hecho en el ADN plugin configuración para
la gama local nueva. Específicamente, El dnaNextRange atributo de 'cn=Posix
IDs,cn=Tarea Numérica Distribuida Plugin,cn=plugins,cn=config' tiene que ser
modificado para emparejar la gama nueva.
08/20/2026
User avatar None

String updated in the repository

Manage CA ACL rules.

This plugin is used to define rules governing which principals are
permitted to have certificates issued using a given certificate
profile.

PROFILE ID SYNTAX:

A Profile ID is a string without spaces or punctuation starting with a letter
and followed by a sequence of letters, digits or underscore ("_").

EXAMPLES:

Create a CA ACL "test" that grants all users access to the
"UserCert" profile:
ipa caacl-add test --usercat=all
ipa caacl-add-profile test --certprofiles UserCert

Display the properties of a named CA ACL:
ipa caacl-show test

Create a CA ACL to let user "alice" use the "DNP3" profile:
ipa caacl-add-profile alice_dnp3 --certprofiles DNP3
ipa caacl-add-user alice_dnp3 --user=alice

Disable a CA ACL:
ipa caacl-disable test

Remove a CA ACL:
ipa caacl-del test

Dirige CA ACL reglas.

Esto plugin suele definir las reglas que rigen qué principals es
permitted para tener los certificados emitieron utilizar un perfil de
certificado dado.

Perfil ID SINTAXIS:

Un Perfil ID es una serie sin los espacios o la puntuación que empiezan con una letra
y seguido por una secuencia de letras, dígitos o underscore ("_").

Ejemplos:

Crear un CA ACL "prueba" que becas todo acceso de usuarios al
"UserCert" perfil:
ipa caacl-añadir prueba --usercat=todo
ipa caacl-añadir-prueba de perfil --certprofiles UserCert

Mostrar las haciendas de un nombrados CA ACL:
ipa caacl-prueba de espectáculo

Crea un CA ACL para dejar usuario "alice" utilizar el "DNP3" perfil:
ipa caacl-añadir-perfil alice_dnp3 --certprofiles DNP3
ipa caacl-añadir-usuario alice_dnp3 --usuario=alice

Inutilizar un CA ACL:
ipa caacl-inutilizar la prueba

Saca un CA ACL:
ipa caacl-del prueba
08/20/2026
User avatar None

String updated in the repository
Rename the User ID override object
Renombrar el permiso del objetodo del objeto del registro de recurso DNS
08/20/2026
User avatar None

String updated in the repository
Results should contain primary key attribute only ("anchor")
Los resultados deberían contener solo la clave del atributo primario ("namemap")
08/20/2026
User avatar None

String updated in the repository

Groups of users

Manage groups of users. By default, new groups are POSIX groups. You
can add the --nonposix option to the group-add command to mark a new group
as non-POSIX. You can use the --posix argument with the group-mod command
to convert a non-POSIX group into a POSIX group. POSIX groups cannot be
converted to non-POSIX groups.

Every group must have a description.

POSIX groups must have a Group ID (GID) number. Changing a GID is
supported but can have an impact on your file permissions. It is not necessary
to supply a GID when creating a group. IPA will generate one automatically
if it is not provided.

EXAMPLES:

Add a new group:
ipa group-add --desc='local administrators' localadmins

Add a new non-POSIX group:
ipa group-add --nonposix --desc='remote administrators' remoteadmins

Convert a non-POSIX group to posix:
ipa group-mod --posix remoteadmins

Add a new POSIX group with a specific Group ID number:
ipa group-add --gid=500 --desc='unix admins' unixadmins

Add a new POSIX group and let IPA assign a Group ID number:
ipa group-add --desc='printer admins' printeradmins

Remove a group:
ipa group-del unixadmins

To add the "remoteadmins" group to the "localadmins" group:
ipa group-add-member --groups=remoteadmins localadmins

Add multiple users to the "localadmins" group:
ipa group-add-member --users=test1 --users=test2 localadmins

Remove a user from the "localadmins" group:
ipa group-remove-member --users=test2 localadmins

Display information about a named group.
ipa group-show localadmins

External group membership is designed to allow users from trusted domains
to be mapped to local POSIX groups in order to actually use IPA resources.
External members should be added to groups that specifically created as
external and non-POSIX. Such group later should be included into one of POSIX
groups.

An external group member is currently a Security Identifier (SID) as defined by
the trusted domain. When adding external group members, it is possible to
specify them in either SID, or DOM\name, or name@domain format. IPA will attempt
to resolve passed name to SID with the use of Global Catalog of the trusted domain.

Example:

1. Create group for the trusted domain admins' mapping and their local POSIX group:

ipa group-add --desc='<ad.domain> admins external map' ad_admins_external --external
ipa group-add --desc='<ad.domain> admins' ad_admins

2. Add security identifier of Domain Admins of the <ad.domain> to the ad_admins_external
group:

ipa group-add-member ad_admins_external --external 'AD\Domain Admins'

3. Allow members of ad_admins_external group to be associated with ad_admins POSIX group:

ipa group-add-member ad_admins --groups ad_admins_external

4. List members of external members of ad_admins_external group to see their SIDs:

ipa group-show ad_admins_external
 
08/20/2026
User avatar None

String updated in the repository

Verify replication topology for suffix.

Checks done:
1. check if a topology is not disconnected. In other words if there are
replication paths between all servers.
2. check if servers don't have more than the recommended number of
replication agreements
 
08/20/2026
User avatar None

String updated in the repository
LDAP suffix to be managed
 
08/20/2026
Browse all changes for this language