Unsolved

2 Intern

 • 

30 Posts

 • 

12 Points

189

June 23rd, 2026 18:28

Dell OpenManage proxy password issue

Seems that the latest update (4.7.0) broke proxy functionality. I've tried disabling and re-enabling proxy, but now the console doesn't allow our password for proxy auth.

Seems to be enforcing a complex password, which it should NOT be doing considering the password enforcement is done on the proxy side, not the OME side.

1 Attachment

Moderator

 • 

3.8K Posts

 • 

25.5K Points

July 1st, 2026 10:34

Quick Workarounds
  • Use the REST API: Bypass the broken Web UI by pushing your proxy credentials directly via the OME API using curl or Postman.
  • Inspect Element: Press F12 in your browser, select the grayed-out "Apply" button or password field, and delete the disabled or validation attributes to force-click it.
  • Use IP Instead of FQDN: Switch the proxy address from a hostname (e.g., proxy.local) to an IP address, which sometimes bypasses validation loops.
Recommendation
Open a ticket with Dell Support so engineering can log this UI bug and potentially provide a backend database fix.

2 Intern

 • 

30 Posts

 • 

12 Points

July 6th, 2026 16:15

Thanks, are the supported API calls documented anywhere? Tried switching the proxy from FQDN to IP, but that didn't work, and the "Apply" button isn't grayed-out, it allows me to click, but then shows the error I included in the original post.

Moderator

 • 

3.8K Posts

 • 

25.5K Points

July 7th, 2026 06:08

 

Hi,

yes here:

https://dl.dell.com/topicspdf/dell-openmanage-enterprise_reference-guide8_en-us.pdf?dgc=SM&cid=243906&lid=spr5925610022&RefID=dtw22_sm5925610022&linkId=140436340

 

However, there seems to be an issue in the proxy library we use in OME, which introduced a change in 4.7 that enabled password complexity requirements for this field in the web UI.

 

The new requirements are documented in the 4.7 User's Guide - Dell OpenManage Enterprise 4.7 User's Guide, page 62.

2 Intern

 • 

30 Posts

 • 

12 Points

July 7th, 2026 15:19

Thank you for this. I'm able to update the password via API, however the proxy exclusion now gets reset. And I'm unable to update it via API as that's not an available resource, and I'm not able to update it via web console as that requires I enter the unacceptable password. So as it stands, this is definitely a bug that breaks proxy functionality.

Moderator

 • 

3.8K Posts

 • 

25.5K Points

July 8th, 2026 03:58

Hi 

With 4.8 it could be resolved probably.The Devs are informed about this.

1 Rookie

 • 

14 Posts

 • 

47 Points

August 19th, 2026 12:33

@Dell-Martin S​ 

I ran into the same issue and tried to set the proxy password with Ansible. I suppose it's using the same API? Does the API also enforce the new password rules? It looks like it does, the error message is the same as in the UI. Or is there a way around that?

Background: We have a central proxy user for these kind of access and it's used for several devices. If I change that, I have to change it on all of them... which sux.

How does the solution look like? Relax the password rules again in 4.8? You should at least adjust the error message. Currently it allows just wild guessing.

Moderator

 • 

28 Posts

 • 

63 Points

August 20th, 2026 11:39

Hi _Armin_,

 

Here is what we can suggest at this time.

 

Temporary proxy bypass - If feasible for your environment, temporarily disable proxy functionality until 4.8 is available (though this may not be practical depending on network requirements)

Long-term Solution:

This behavior is observed due to the proxy library used in OME 4.7.0 and the official fix will be in OME 4.8, which should:

  • Remove the inappropriate password complexity enforcement for proxy authentication

  • Improve error messages to provide clearer guidance

Recommendation: Monitor for OME 4.8 release and upgrade as soon as it's available. In the meantime, work with your proxy administrator to create an OME-specific proxy account that meets the current requirements, or coordinate a password change across all devices if the central proxy user must be updated.

 

Regards,

DELL-Bridjet V

Social Media and Communities Professional

Dell Technologies | Enterprise Support Services

#IWork4Dell

Was your query answered? Please click Thumbs Up to Mark it as Accepted Answer!

1 Rookie

 • 

14 Posts

 • 

47 Points

August 20th, 2026 18:05

@DELL-Bridjet V​ Thanks for the info.

The proxy is necessary and cannot be reconfigured. Currently I'm using a spare user with a separate password. This way I'm able to get updates and images again.

Do you have an idea about when (roughly) 4.8 is released? The UI of 4.7 is terrible and our productivity is drastically reduced because of that. We desperately looking forward for 4.8 :-)

Moderator

 • 

28 Posts

 • 

63 Points

August 21st, 2026 04:37

Hi _Armin_,

Thank you for sharing your workaround — using a spare user with a separate password is a practical solution. I understand you are eagerly looking forward to the release of version 4.8 given the impact of the 4.7 UI on productivity.

 

Unfortunately, I couldn't find any information regarding the release date for version 4.8 at this time. We will just have to keep an eye out for any official updates.

 

Regards,

DELL-Bridjet V

Social Media and Communities Professional

Dell Technologies | Enterprise Support Services

#IWork4Dell

Was your query answered? Please click Thumbs Up to Mark it as Accepted Answer!

No Events found!

Top