Port reverts to 80 from 443 in Account document

I have an Account document in my personal NAB (and therefore my Preferences, for a sidebar widget that needs to use port 443. However, every time I try to set it to use port 443, and set the server as https://targetserver.com, it reverts to 80 and http://targetserver.com. This happens whether I create the account from my PNAB or the preferences.

I’ve tried setting the protocol as Other, with 443 as the destination port in the PNAB, and HTTP/HTTPS with https:// and 443 in the preferences, and every time it reverts to http:// and port 80.

This means the widget fails, as port 80 access to the destination server is blocked by our (fairly arbitrary) firewall rules.

Can anyone help me get my settings to stick?

For information, I do not have any policies applied to my account.

Subject: Need Help Reproducing

I have been trying to reproduce this issue and I am not able to. Can you give me the set of steps you are taking so I can try to follow the exact steps?

Subject: Steps to recreate

  1. Create the account in Preferences, Accounts:

Ok that, twice (once for the account, once for the Preferences.

The address book immediately shows it as an HTTP only account:

but Preferences still shows the server address as https://…

Go to the account document and it displays 443 as the port

Advanced

Port number:

443

and https://… in the ServerName field

(Then have to wait while I restart Notes because I’d previously removed TwitNotes and had to reinstall it)

After relaunching, and filling in the ID and Login in the Widget itself

Now, it’s entirely possible that this is the widget itself causing the problems (but I doubt it), so Mikkel, if you’re listening, is there any light you can shed?

But I don’t think so.

It should be noted that the above screenshots were taken from NOT behind the company firewall. And the widget does actually work here on port 80, but if I can’t get it to stay on port 443, where my username and password are at less risk, I don’t want to use it.

I also not that on the account form in the design of the Personal NAB, the Input Translation event switches to 80 if the protocol is HTTP, and there’s no HTTPS protocol. When I’ve set the protocol to Other, the port to 443, and the URL to begin https://… it will still revert back to protocol HTTP, port 80, and URL to http://…

Please help, there’s a whole world of less than earth shattering minutiae I’m missing out on ;o).

Subject: More Questions

Thanks for the detailed steps. I need a little more info…

  1. Did you create your account from scratch, or are you editing an account that was created by widget creation?

  2. Do you have any other accounts that are for twitter.com?

  3. Can you give me the xml for your widget? (Export the widget to an xml file). This will give me a lot of detail about how the widget is configured.

  4. When you say this: “After relaunching, and filling in the ID and Login in the Widget itself”, where are you filling in the ID: in a dialog that pops up when launching the widget (like the one below)? I am trying to replicate this issue with your steps. The fact that you have to enter the credentials twice (first time was in your first step of account creation) seems a bit off here.

Subject: Responses

Doug

  1. Tried it both ways.

  2. No

  3. This db doesn’t allow attachments (understandable, really), but here’s a link to it in TurtlePartnership’s Widget catalog → .

  4. I’ve tried both here:

and here:

As I said, it may well be the widget itself that’s doing the overwriting.

Subject: Custom widget

The widget that you are using is a custom widget that installs features/plugins. So it is only installing the application that you are using. The application itself if the one that is most likely changing your account type. I see a CredentialManager.class which could be making changes.

Subject: Thanks Doug

I thought it might be something like that once I started looking at the plugin itself, and the CredentialManager may be at the heart of it.