Provisioning for SPA942 with HTTP Authentication

Unanswered Question

Is this the correct format for the profile rule to have the phone use basic http authentication and get an encrypted file?

[--uid username --pwd password --key encryptionkey] https://config.server.com/configs/client/extension.cfg

I currently can successfully provision my phones using the rule as:

[--key encryptionkey] https://config.server.com/configs/client/extension.cfg

Once I try to add http authentication the phone logs 'Resync failed: https_get failed' but there is no authentication error logged by Apache.

Any help would be appreciated.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Alberto Montilla Wed, 10/21/2009 - 05:56

Dear Sir;

I suggest you have a look at the provisioning guide first if you have not done it already. If so, please let me know.

Regards
Alberto

Alberto Montilla Mon, 10/26/2009 - 04:56

Dear Sir;

It looks like you are trying to use https (not exactly http authentication), could you please clarify exactly what protocol you would like to use?

https is supported widely, you need server certificate signed by Cisco as well as the CA, also provided by us.

In case you require http authentication, I need to check with engineering whether this is widely available, as this has been introduced to work in conjunction with the Extension Mobility feature set.

I'll let you know on the later.

Regards
Alberto

Actions

This Discussion