Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 5 replies
  • Subscribers 1 subscriber
  • Views 7457 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Secondary credentials - password gets erased

Sladey

Hi,

We are running Spohos Administration Console V4.7.0.13.

We have a secondary update server of Sophos configured and all the various updating policies have the username and password configured.

When Sophos is pushed out to clients, the username field is populated however the password field is not. This has the effect of not permitting machines to update if they are not connected to our internal network.

I have tried creating a new update policy and pushing that out instead of the existing policies but to no avail.

Any suggestions welcomed.

Sladey

:37215


This thread was automatically locked due to age.
Parents
  • 0

    Hello Sladey,

    I did not doubt that you did enter a password. SEC4.7 is long gone from my systems, dunno if the GUI has changed since then. Can't say what the problem could be. First, editing the policy in SEC - does the password "stick"? I.e. if you check the Specify secondary server details for the first time, the Password: field gets enabled and is blank. If you enter a password dots appear which should be there after saving and opening again the policy. From now on you can't write into the field directly but have to click Change. Is this the case?

    Don't think there were significant changes in the GUI between 4.7 and 5.x - the dialog seems pretty watertight, at least I've found no sequence of actions which could produce unexpected results, e.g. due to a missing warning. And I don't think it does behave like the SUM configuration and checks the credentials (and if, I'd expect a warning).

    Christian

    :37231
Reply
  • 0

    Hello Sladey,

    I did not doubt that you did enter a password. SEC4.7 is long gone from my systems, dunno if the GUI has changed since then. Can't say what the problem could be. First, editing the policy in SEC - does the password "stick"? I.e. if you check the Specify secondary server details for the first time, the Password: field gets enabled and is blank. If you enter a password dots appear which should be there after saving and opening again the policy. From now on you can't write into the field directly but have to click Change. Is this the case?

    Don't think there were significant changes in the GUI between 4.7 and 5.x - the dialog seems pretty watertight, at least I've found no sequence of actions which could produce unexpected results, e.g. due to a missing warning. And I don't think it does behave like the SUM configuration and checks the credentials (and if, I'd expect a warning).

    Christian

    :37231
Children
No Data