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
48%
Browse Translate
118,459 Words
22%
814,325 Characters
20%

Strings status

Strings Words Characters
9,824 118,459 814,325
All strings Browse Translate Zen
4,900 27,295 176,495
Translated strings Browse Translate Zen
4,924 91,164 637,830
Unfinished strings Browse Translate Zen
3,367 84,116 589,936
Untranslated strings Browse Translate Zen
1,557 7,048 47,894
Strings marked for edit Browse Translate Zen
1,397 5,897 39,298
Strings with suggestions Browse Translate Zen
3,738 85,899 602,884
Unfinished strings without suggestions Browse Translate Zen
720 3,592 24,790
Strings with any failing checks Browse Translate Zen
162 1,063 6,787
Translated strings with any failing checks Browse Translate Zen
22 46 379
Translated strings with dismissed checks Browse Translate Zen
34 67 520
Failing check: Unchanged translation Browse Translate Zen
25 125 1,025
Failing check: Starting newline Browse Translate Zen
46 169 1,225
Failing check: Trailing newline Browse Translate Zen
4 8 59
Failing check: Starting spaces Browse Translate Zen
10 69 541
Failing check: Trailing space Browse Translate Zen
4 8 59
Failing check: Double space Browse Translate Zen
359 2,103 14,008
Failing check: Mismatched full stop Browse Translate Zen
16 41 251
Failing check: Mismatched colon Browse Translate Zen
3 17 97
Failing check: Mismatched question mark Browse Translate Zen
142 555 4,103
Failing check: Multiple capitals Browse Translate Zen
97 520 3,825
Failing check: Python format Browse Translate Zen
91 596 4,375
Failing check: Python brace format Browse Translate Zen
78 350 2,356
Failing check: Inconsistent Browse Translate Zen
57 276 2,102
Failing check: Mismatching line breaks Browse Translate Zen
5 20 140
Failing check: Consecutive duplicated words 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 58% 2,050 43,856 307,015 2,050 51 516
stable-release GPL-3.0-only 41% 2,874 47,308 330,815 1,317 669 881

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 Indonesian
Language code id
Text direction Left to right
Case sensitivity Case-sensitive
Number of speakers 180,519,583
09/16/2026

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 9,824 118,459 814,325
Translated 49% 4,900 23% 27,295 21% 176,495
Needs editing 15% 1,557 5% 7,048 5% 47,894
Read-only 0% 0 0% 0 0% 0
Failing checks 7% 720 3% 3,592 3% 24,790
Strings with suggestions 14% 1,397 4% 5,897 4% 39,298
Untranslated strings 34% 3,367 71% 84,116 72% 589,936
Last 12 months Previous

Activity in last 12 months

2 changes 0 changes 3 changes 3,460 changes 2 changes 60 changes 0 changes 233 changes 0 changes 257 changes 0 changes 885 changes 0 changes 153 changes 14 changes 0 changes 0 changes 0 changes 0 changes 1,208 changes 2 changes 11,952 changes 1 change 5,253 changes
SepOctNovDecJanFebMarAprMayJunJulAug

Quick numbers

118 k
Hosted words
9,824
Hosted strings
49%
Translated
6
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/id.po” file was changed. 08/20/2026
User avatar None

String updated in the repository
GSSAPI|EXTERNAL
 
08/20/2026
User avatar None

String updated in the repository
url
 
08/20/2026
User avatar None

String updated in the repository
Path to the IPA CA certificate
harus merupakan sebuahBerkas untuk menyimpan sertifikat.
08/20/2026
User avatar None

String updated in the repository
LDAP password
Masukkan kata sandi LDAP
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

Add new ID range.

To add a new ID range you always have to specify

--base-id
--range-size

Additionally

--rid-base
--secondary-rid-base

may be given for a new ID range for the local domain while

--rid-base
--dom-sid

must be given to add a new range for a trusted AD domain.

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.
 
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.
 
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
 
08/20/2026
Browse all changes for this language