Adding License Key to Asset HTTP Error 500

AMConsulting

I just installed ITFlow the past week as it was recommended to me from a colleague. When attempting to add a license to an asset, it errors and gives me an HTTP Error 500. I can create the asset without the license, but when I add the license (one of those encrypted keys) is when I get the error. I've seen other posts about a character limit in the DB or checking PHP logs. The license is 210 characters with a number of dashes and forward slashes, if that makes a difference.

If anyone can guide me (with details, please), I'd be greatly appreciative.

Thanks

Alan

One thing I ran into importing assets last week, I eventually tracked down to the characters, by using Notepad++ on the csv file. It turned out that there were 3 variants of " (double quotes). One vertical, and one each slanted both ways. This was for strings, so it didn't matter and I replaced all to the vertical double quote marks, then it imported the assets fine.

The issue there, was that there was no feedback as to why it was failing, and it would import a few assets each time… just a case of trying different things until I found the cause of the problem. Hope it helps, but altering characters in an encrypted key… probably not advisable.

AMConsulting

Thanks Alan. I'll download and check with Notepad++. In the license key, there are a number of forward slashes. It's possible that, in combination with the following letter, could be creating an issue with saving the DB. I'm not importing a CSV, however, simply using the GUI to add the key.

wrongecho

Hey @AMConsulting - thanks for reporting.

I've tested and this relates to a database column size limit ("Fatal error: Uncaught mysqli_sql_exception: Data too long for column 'login_password' at row 1 in itflow\post\login.php on line 14").
I've mentioned elsewhere but we do not currently limit input size anywhere in the app 🙁. We could start doing soft limits via HTML and then enforcing these in PHP but it's a big task that honestly doesn't come up all that often as an issue.
Also, the username and password fields are encrypted which means that the amount of characters you put in isn't necessarily the amount of characters that are output.

@johnny - Would you have any objection to increasing the login_username and login_password fields to be 500 chars? Also, any idea why the login_password field is a varbinary??

johnny

Hey @wrongecho softlimits sounds good technically we could just specify a input size limit a input size limit input size limit c … var during the session then apply that var across the input fields.

Im not 100% sure why the login password is varbinary

AMConsulting

@wrongecho

Thanks for the reply. This license key is 227 characters (including dashes, forward slashes, and underscores). If there was a way to attach the key as a text file or other file, that could be an alternative. I don't know how you have this configured on the backed.

In general, vendors are using these encrypted keys for licenses and I don't know the overall lengths. In my specific case, I purchased 8 licenses (each 227 characters). For the license entry, I set 8 licenses and then wanted to add the assets they are used for, but I can't even add the single license.

While you consider how to fix this, you should keep this in mind (I may end up with 20 or 30 licenses for the same software), or I can just create a single license entry for each of the 8 licenses and assign them to the individual asset. But I'd need it to hold at least 227 characters.

At the least, the error handling needs to be fixed so we know the errors on entry.

Thanks for all the work that goes into this. I'm really enjoying the software so far.

wrongecho

Thanks for coming back to me 🙂

This license key is 227 characters

This will be the issue. We'll bump the password length in the database as this has come up a few times.

While you consider how to fix this, you should keep this in mind (I may end up with 20 or 30 licenses for the same software), or I can just create a single license entry for each of the 8 licenses and assign them to the individual asset. But I'd need it to hold at least 227 characters.

Alternatively, have you considered creating a single software entry and then storing the different license keys in the "Software Notes" section (assuming the keys don't need to be encrypted at rest)? It seems a little redundant to create 8 login entries, but I get it as we currently assume you'll only have 1 license key per software (which also has a 200 char limit).

JosephWithCOR

wrongecho Alternatively, have you considered creating a single software entry and then storing the different license keys in the "Software Notes" section

Doing it this way makes tying a license to an asset that much more work to sort out.

AMConsulting

Sorry for the delay in responding. I added the license keys to the Software notes section. I'll have to track each license and device that way, but it works for me.

Thanks

wrongecho

AMConsulting

Thanks for confirming.

We should still probably increase the password length field in the database to account for edge cases like this.