Need explanation on new SSL Enom Integration

[worsin]

After signing up to a cert through enom WHM generates a USERNAME and PASSWORD.

 

See screenie

 

http://www.hostrocks.com/images/whatsthis.png

 

Question is whats it for?

 

BTW everything seems to run smooth did it in test mode with no issues. Have to add your IP and turn on the test server but that was simple to do. Have not tried live yet.

 

Also does this feature do anything other than upload the order made into Enom? Seems no other info carries over ie the customer address etc.

 

Can anyone help me understand the best way to have customer generate the signing request?

 

Please forgive all the questions i just want to fully understand what i need to do to make this a smooth process.

[Matt]

1. The username and password can be ignored - they are generated whenever a module runs a creation routine but aren't used in the case of SSL Certificates

 

2. Once the user has ordered and paid for the SSL certificate, they get an email containing a link to Configure the Certificate on your site. The email template for that is "SSL Certificate Configuration Required"

 

3. For more info, see http://wiki.whmcs.com/Enom_SSL_Certificates

 

Matt

[brianr]

nevermind...

[opt2bout]

3. For more info, see http://wiki.whmcs.com/Enom_SSL_Certificates

Matt,

 

I'm a little confused on how to use the configurable options to allow the user to select the certificate type and number of years without creating a single product for each certificate type.

 

Is there a way to configure it in this way, or is it best to create a separate product for each cert type, and then use the configurable option "Years" to manually enter the cost?

[Ben-iNetFx]

Matt,

 

I'm a little confused on how to use the configurable options to allow the user to select the certificate type and number of years without creating a single product for each certificate type.

 

Is there a way to configure it in this way, or is it best to create a separate product for each cert type, and then use the configurable option "Years" to manually enter the cost?

That's what I've done, created all the certs seperately and just used the Years configurable option.

 

Only thing that got me was the payment scheduling. In the end I guessed they are setup as "one time" products (or is WHMCS smart enough to know if you config option a cert to 5 years, it adds 4 years onto the 1 year recuring date?)

[Richie]

That's what I've done, created all the certs seperately and just used the Years configurable option.

 

Only thing that got me was the payment scheduling. In the end I guessed they are setup as "one time" products (or is WHMCS smart enough to know if you config option a cert to 5 years, it adds 4 years onto the 1 year recuring date?)

 

Wouldnt mind knowing that too, was playing with the demo and see that it has the 1 to 10 years drop down, how exactly does that charge correctly and pass over to enom because in the demo, regardless of what you set, this part is hidden.

 

Do you need to then set a new product for every years option?

 

I see the wiki says:

 

" The option names supported to overide the default settings are "Certificate Type" and/or "Years" - you can use both, one or neither."

 

Can you give us a screenshot example of how and where to use these please somebody?

[Richie]

Having now upgraded to the new 3.6.2, this enom SSL thing is a bit confusing, so hopefully if I ask this the right way, it might make some sense so others might either know the answer, or might also be having the same confusion.

 

We create a product "GeoTrust QuickSSL" for example, set a price of £70 for example, and in the "Module settings" it is set to 1 years from the drop down list of 1 to 10 years.

 

So far all is ok....

 

The confusion starts when you can set adjustable options using "Configurable options" as described in the WIKI so that you can offer more years.

 

So, I went ahead and set more years in the "Configurable options" so that 0 is the default additional years and customers selecting the drop down for more years can change the cost by adding more years to the certificate...

 

What I'd like to know is...

 

If I now purchase a cert for example and select 2 additional years, then pay for it (making a 3 year certificate), how does this get passed to enom as a 3 year certificate, or does it remain a 1 year certificate as I had already set in the "Module settings" screen dropdown of 1 to 10?

 

Confused?

 

I'm basically asking, do the "configurable options" over-ride the "module settings" if enabled and does this then get passed to enom for the number of years purchased, or is manual intervention required upon a customer ordering additional years?

 

Would really love to know asap so we can get this working and running pronto as its a fantastic new feature from Matt.

 

Also, the billing periods for the configurable options only allow annually and bi-annually, so if I were to add a 5 year certificate, wont this try to bill the customer for it annually/bi-annually? How do we offer 3+ year certificates if the WHMCS doesnt allow us to set the pricing any more than every 2 years?

 

I'd hate to sell a ton of 3+ year certificates only to have customers wondering why its being invoiced for renewal 12 months later...

 

Help somebody ?

[Richie]

Just an afterthought on this one...

 

Are we meant to set "recurring" or "One time" billing for these certificates?

[penguin]

I'm guessing that it will have to be one time. Cert expiry dates can alter when they come up for renewal as Geotrust for example can add up to 3 months to the expiry date. Also, if set to recurring, what then happens when customers cards are automatically charged - how is the renewal handled with the registry, as normally you need to complete the same procedure of submitting your CSR again. If set to one-time, they will be e-mailed by the registry when the cert is expiring, and so then just order a new certificate to renew/replace the certificate.

[Richie]

One-time billing could really get messy as WHMCS wont send out renewal reminders and the customers "products" listings will just keep growing with the same products when simply adding more years to the already existing "recurring" price boxes would have worked a treat.

 

Anyway, no offence intended but I was hoping for something a little more official than guess work, as thats where I'm already at.

[Matt]

My recommendation would be that you setup a product for each type of certificate (rather than a configurable option for choosing that) and then have the years as a configurable option only. The billing type needs to be setup as One Time and the configurable options for the years then setup with the prices in the Monthly field to alter the one time price during ordering.

 

Matt

[Richie]

Thaks for clarifying that a bit more Matt, but one of my questions was also to ask what happens to or how are the year variables used?

 

On the "Module settings" tab of each certificate you have this dropdown to specify "Years", yet the configurable options allows the customer to select more years, purely for the function of changing the price...

 

so what I was concerned about is a customer selecting 2/3/4/5 years or more, yet only the 1 yera being passed to Enom as specified in the "Module settings" tab?

 

Also, if its "one time billing" only, does WHMCS send out a reminder to let a customer know when this one time product is due to expire?

[Matt]

Thaks for clarifying that a bit more Matt, but one of my questions was also to ask what happens to or how are the year variables used?

 

On the "Module settings" tab of each certificate you have this dropdown to specify "Years", yet the configurable options allows the customer to select more years, purely for the function of changing the price...

 

The option names supported to overide the default settings are "Certificate Type" and/or "Years"

 

The above quote from the documentation is where it explains what will happen - the configurable option selection will overide the module setting.

 

Also, if its "one time billing" only, does WHMCS send out a reminder to let a customer know when this one time product is due to expire?

No, as a one time product there's no expiry date. If you want to have renewal notices you'll need to limit your offerings to 1 or 2 years (the recurring cycles WHMCS supports).

 

Matt

[Troy]

No, as a one time product there's no expiry date. If you want to have renewal notices you'll need to limit your offerings to 1 or 2 years (the recurring cycles WHMCS supports).

 

Matt

 

Questions, assuming we do the above so that the certificate can be renewed by the customer:

 

1. Like other products, will WHMCS generate a renewal invoice?

2. Like other products, can the customer cancel to indicate he no longer wishes to maintain the certificate?

3. Will the administrator know there has been a renewal, if manual intervention is required?

4. Will WHMCS automate the renewal so the admin does not have to intervene?

[Pima]

Tried to follow the setup for this according to recommendations made by Matt.

 

Pricing:

Onetime:

tried set to "0"

Tried set to the one year price

Tried to enter "Years" unsuccessfully

 

Module Settings:

ENOMSSL

others default

 

Configurable options - Years

1 yr

3 yr

5 yr

each with a total price for term

 

On the order side the drop down for the term is displayed and can be selected - but the order prices is not incremented??

 

It displays either "0" or the one year price no matter the term selected.

 

What have I missed?

[Richie]

Tried to follow the setup for this according to recommendations made by Matt.

 

Pricing:

Onetime:

tried set to "0"

Tried set to the one year price

Tried to enter "Years" unsuccessfully

 

You dont put "years" anywhere in the pricing options. Only price's for the current billing terms.

 

Module Settings:

ENOMSSL

others default

 

Dont forget to pt in your enom username and password, this needs to be done for every certificate.

 

Configurable options - Years

1 yr

3 yr

5 yr

each with a total price for term

 

On the order side the drop down for the term is displayed and can be selected - but the order prices is not incremented??

 

It displays either "0" or the one year price no matter the term selected.

 

What have I missed?

 

Why would you have a configurable option of "1 year" when the certificate is already 1 year minimum.

 

We tried this and it was fine, we put the first option as 0 extra years, which is the default, thus allowing the single 1 year purchase, then the 1,2,3,4 extra years with the appropriate costings into WHMCS and when selected during the checkout it add's it up correctly, albeit via trial and error.

 

Sadly this new functionality is really lacking any proper instructions, and only has bare minimum guidance in the Wiki. Seems that WHMCS think we all know their system the way they do and should understand this as soon as we look at it.

 

A few screenshots of each section with notes on filling in each part would have been really ideal, especially as we are all seeing this for the first time and have no idea "Exactly" what goes where, its easy to get this all messed up.

[Richie]

ok so we've switch the pricing to non-recurring, but now in the cart it shows the prices all as "£x.00 One Time" not giving any indication that its billed annualy or that the cost is for 1 year/per year.

 

Doesnt sound like a big deal maybe but I've fore-seeing problems upon renewal here when a customer says "But your order said One Time, not per year or annually"

 

I think the only way to do this sensibly would to use it as a recurring product so that it shows correctly in the purchasing phase, but then we may need to create a custom welcome email to advise that SSL certificates are only valid for the time period purchased.

 

If done as a one time only, try explaining to a customer that they need to order another one instead of renewing the one they already have when other SSL suppliers simply give the option to renew existing certificates.

 

Matt, if we do it as a recurring product, there isnt any "renew" button in the admin side, does the ENOM API allow for renewing certificates or do they work totally on a "buy another one when it expires" priciple?

[Matt]

Troy:

 

1. Yes, if setup as a recurring product

2. Yes, exactly the same as with any product/service

3. As far as I'm aware, there is no API command to renew a certificate and so no renew button/option currently for the SSL products.

 

Richie:

 

The minimum years configuration option on the product should be 1 Year. The years field should show all the available year offerings you want clients to have as the years configurable option does not add onto the default setting - it overides it.

 

The one time/recurring clarification is something you could do as part of the product description or like you say use the recurring options and just offer the 1/2 year options which that allows. Then renewals will be invoiced and reminders sent also so would help you on both fronts.

 

Matt

[Boss]

Matt

Coming from the other thread I started http://forum.whmcs.com/showthread.php?p=68422#post68422 to this one you recommended.

 

The first REALLY BIG issue with all of this is the billing period/s.

Would it not be easier, both in the Standard product Pricing field area and the Configurable Options pricing to just have One Field that ask's, "Billing Period".

Here you insert the billing period, which could be configured to accept months or to be even more flexible Days.

So for a 1 year period you simply enter, "365" (Days).

A 5 Year period enter, "1825" (Days) and so on. I think most people can use a calculator to work out the days thing.

This totally eliminates the billing periods problem, as this can be applied to coincide with domain names as well or anything you like.

 

 

Troy:

The minimum years configuration option on the product should be 1 Year. The years field should show all the available year offerings you want clients to have as the years configurable option does not add onto the default setting - it overides it.

Matt

This section here (as above), I don't understand.

Where does the years options override anything. It does not seem to matter where or how I put extra year options in, if I want a 2 year SSL I get charged three years.

I just don't get it.

For the moment there is couple of ways out of this that will definitely work, because the configurable options have not as yet been thought out enough.

1. Don't bother with them at all.

2. Offer only 1 year SSL's, only.

2. Set up each cert, Twice. Once for a 12 month period and a second for a Bi-Annual billing period.

 

The Config Options just don't work at all, and there is still to many unanswered(or confirmed) questions.

 

Like, what Does this mean?

"The option names supported to override the default settings are "Certificate Type" and/or "Years" - you can use both, one or neither."

This either is not working or I'm just completly loosing it and not looking at things in a logical way anymore.

[brianr]

-SNIP-

 

Would it not be easier, both in the Standard product Pricing field area and the Configurable Options pricing to just have One Field that ask's, "Billing Period".

Here you insert the billing period, which could be configured to accept months or to be even more flexible Days.

So for a 1 year period you simply enter, "365" (Days).

A 5 Year period enter, "1825" (Days) and so on. I think most people can use a calculator to work out the days thing.

 

-SNIP-

 

2 words - Leap Years.

 

If you make configurable billing periods (+1 from me) you need to allow any combination of days, weeks, months and years, then let PHP do that date-math in a leap-year friendly way. This you if you have a year and a half-cycle, you can do 1 year 6 months - easier to read then 18 months.

 

Anyway back to your problem...

 

Is your year configurable option called "Years" and the Options "1", "2", "3", etc? If you have "1 Year" as an option I don't think it works.

[Inetbiz]

What I did is set the recurring base annual price. On the configurable options, 1 = 0, 2=1st year amount, then year 3 = base year x 2, etc. So far it works well. Why on earth can WHMCS only support recurring billing notices for years 1,2? If the array number of rows says 5, increment until array # rows = # of notifications.

[Inetbiz]

Here's a real stumper! Can I turn on domain options? Why not sell a domain and an SSL but heck, one of the options is to use own nameserver isn't it?

[Inetbiz]

follow up.. I hope it's not going to try and isntall it on the default server? If the client does not host with us, it makes NO sense to setup the SSL?

[Boss]

Is your year configurable option called "Years" and the Options "1", "2", "3", etc? If you have "1 Year" as an option I don't think it works.

 

Hi Brian

Thanks for your comments.

Yes I had Years and Options as 1, 2, 3, etc.

I have now gone down the way of adding each cert twice, one for a One year period and the other for a two year period, both recurring.

 

I really can't see how it can be done any other way at this stage until such time as some major things in the system are plugged.

 

1. Namely billing period needs to be completely reconfigured to allow up to daily billing.

2. The ability to purchase the same product in multiple quantities, by simply adding 2, 3, 4, 10, etc in the Input box, or via drop down list. The same as a normal shopping cart setup.