Two things to consider here:

We don't use "logon" anywhere else in the codebase. "Authentication" is probably more correct here.
"Client" is so general a term that I'm not sure admins are going to understand what this is for as-is.

I think a description would help, and we should mention RBTools in there.
Thinking about the title, though... hmm.. Maybe we make this more broad. Something like:

API Authentication Settings
===========================

<description>

Automatic token expiration: [...]


This gives us a place to expand into if we need to do anything else with authentication later. For example, if we decide to start making password-based authentication optional down the road.

Might make sense at this point to do:

for forms in (self._iter_sso_backend_forms(),
              self._iter_client_web_login_forms()):
    for form, enable_field_id in forms:
        ...


Same with the other form loops below.
In fact, maybe we want to have a method that iterates all these subforms so all these loops dealing with subforms can remain simple, automatically handling new ones going forward? It could do:

yield from self._iter_sso_backend_forms()
yield from self._iter_client_web_login_forms()

No need for parens here.

Formatting should be more like:

widget=AmountSelectorWidget(
    unit_choices=[
        ...
    ],
    number_attrs={
        ...
    }
)


That way there's no confusion about which parts of this belong to the IntegerField vs. the widget.

I don't think anything on this form affects Django settings, so we can probably skip this.

Can we pull these out into a siteconfig_settings variable that get passed in? That'll help avoid the sort of weirdness of the formatting here.

This should be assertIsNone(). Same with similar assertions below.

No trailing period here. Same below.

Ship It!

Ship It!