cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
6038
Views
11
Helpful
3
Replies

Should you always be able to login using fallback domain?

julian.bendix
Level 3
Level 3

Hey folks!

I think I got this wrong, when I read through the Documentation I thought that you can always login using the fallback domain.

I have a local admin user configed for the ACI Fabric and had the impression that I can always login with User apic:fallback\\admin on APIC GUI and with apic#fallback\\admin on APIC and Switch CLI ..

But I seem to be wrong, since I don't manage to use this as login after I configured TACACS+ login as default Realm.

Is this assumption right, or did I mess up my config?

TACACS+ Login works fine.

BR
Jules

2 Accepted Solutions

Accepted Solutions

Sergiu.Daniluk
VIP Alumni
VIP Alumni

By default, the fallback login domain is the local realm. If you haven't change it, then first step is passed.

Second thing which is important, is the setting of "Fallback domain availability" which modify the activation of the fallback domain:

  • Active if ICMP health check fails—The fallback domain becomes active only when all AAA providers in the Default Authentication Realm fail the ICMP health check.

  • Always Active—The fallback domain is always active.

The default setting is Active if ICMP health check fails.

I would suggest you enable the "always available". It is a safe mechanism in case of problems with AAA providers.

Screenshot 2021-11-13 130052.png

 

To access the fallback domain, indeed you have to manually invoked to be utilized. It can be done so with the following syntax:

  • From the GUI, use apic:fallback\\username.

  • From the REST API, use apic#fallback\\username

 

Stay safe,

Sergiu

 

View solution in original post

Hi @julian.bendix,

 

when you configure the authentication on the APIC there is a selection for "fallback check".

If you select false: the APIC will not check if your TACACS server(s) is reachable but always allow to login in with the fallback domain.
If you select true: the APIC will check if your TACACS server(s) is reachable and only if it's not reachable allow to use the fallback domain.


Christoph

View solution in original post

3 Replies 3

Sergiu.Daniluk
VIP Alumni
VIP Alumni

By default, the fallback login domain is the local realm. If you haven't change it, then first step is passed.

Second thing which is important, is the setting of "Fallback domain availability" which modify the activation of the fallback domain:

  • Active if ICMP health check fails—The fallback domain becomes active only when all AAA providers in the Default Authentication Realm fail the ICMP health check.

  • Always Active—The fallback domain is always active.

The default setting is Active if ICMP health check fails.

I would suggest you enable the "always available". It is a safe mechanism in case of problems with AAA providers.

Screenshot 2021-11-13 130052.png

 

To access the fallback domain, indeed you have to manually invoked to be utilized. It can be done so with the following syntax:

  • From the GUI, use apic:fallback\\username.

  • From the REST API, use apic#fallback\\username

 

Stay safe,

Sergiu

 

Hi Sergiu,

thanks a lot for all the info. Makes sense to me.

I just seem to run a older version of ACI I guess, I only have the menu "fallback check" which gives me the options "true" or "false".
If i open the help page, I just get explanations for the options you posted as well, not the options that I have ... 

Screenshot 2021-11-14 231101.png

Hi @julian.bendix,

 

when you configure the authentication on the APIC there is a selection for "fallback check".

If you select false: the APIC will not check if your TACACS server(s) is reachable but always allow to login in with the fallback domain.
If you select true: the APIC will check if your TACACS server(s) is reachable and only if it's not reachable allow to use the fallback domain.


Christoph

Save 25% on Day-2 Operations Add-On License