Enhanced Security Measures in Place:   To ensure a safer experience, we’ve implemented additional, temporary security measures for all users.

Unable to commit config - Invalid Auth Profile After 7.0.5 update

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Unable to commit config - Invalid Auth Profile After 7.0.5 update

L1 Bithead

Hi,

 

We recently updated to 7.0.5 and I cannot commit changes anymore.

 

Error:

______________

Invalid global authentication profile POV-Auth-Profile, only radius auth profile or auth sequence is supported.

Configuration is invalid

Validation Error:

 deviceconfig -> system -> authentication-profile 'POV-Auth-Profile' is not a valid reference

 deviceconfig -> system -> authentication-profile is invalid

 deviceconfig -> system is invalid

 deviceconfig is invalid

 devices is invalid

____________________

 

POV-Auth-Profile is an LDAP Auth Profile.

1 accepted solution

Accepted Solutions

L1 Bithead

Hi Stuart,

 

In the Device>Setup>Management>Authentication Settings>Authentication Profile only RADIUS authentication or Authentication Sequence is supported.

 

As 'POV-Auth-Profile' is an LDAP profile it is giving this error. Although, in previous versions it never throwed any commit error  when there was an incorrect authentication-profile specified in this configuration but now it does as there are certain extra checks added now. 

 

To resolve this you can create an Authentication sequence and add the LDAP Aut Profile to it. You should be able to call this Auth Sequence in Device>Setup>Management>Authentication Settings>Authentication Profile

 

I hope this is helpful.

 

Regards,

Jyoti Singh

View solution in original post

2 REPLIES 2

L1 Bithead

Hi Stuart,

 

In the Device>Setup>Management>Authentication Settings>Authentication Profile only RADIUS authentication or Authentication Sequence is supported.

 

As 'POV-Auth-Profile' is an LDAP profile it is giving this error. Although, in previous versions it never throwed any commit error  when there was an incorrect authentication-profile specified in this configuration but now it does as there are certain extra checks added now. 

 

To resolve this you can create an Authentication sequence and add the LDAP Aut Profile to it. You should be able to call this Auth Sequence in Device>Setup>Management>Authentication Settings>Authentication Profile

 

I hope this is helpful.

 

Regards,

Jyoti Singh

Thanks Jyoti!

 

Had this solved by Palo Support 5 minutes ago, but same solution 😄

  • 1 accepted solution
  • 3834 Views
  • 2 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!