#1 Installation
Get started with the licensing system
Spoiler (Click to View)

#2 Get Server Side Variable
Server side variables are one of the most important pieces to protect your application.
You should store important pieces of information in those server side variables, like stubs or configuration.
You can update the server side variables to show your users messages / news or change the behavior of your application on-the-fly.
Spoiler (Click to View)

#3 Get Posts
You can use posts to show your users messages
Spoiler (Click to View)

#4 Publish Logs
You can use logs to log things like exceptions in your application, or log important things that happen in your application.
Then you can view the logs in your licensing panel.
Spoiler (Click to View)

(Feb 8, 2021 05:02 PM)MavenGradle Wrote:  Why are you sharing code snippets in the form of images?

(Feb 9, 2021 06:10 AM)Shadow_Cloud Wrote:  How searchable/filterable are the logs on the server panel?  Sending logs is the easy part, find the correct info out of millions of log entries is the hard part.

(Feb 9, 2021 06:10 AM)Shadow_Cloud Wrote:  How long are logs stored for?  What's the disk space limit on logs?

(Feb 9, 2021 06:10 AM)Shadow_Cloud Wrote:  Any reason you aren't publishing this as a nuget package so users will automatically see that updates are available?  Including the cs file seems like a strange approach?

(Feb 9, 2021 07:35 AM)neon_light Wrote:  Thank you for the suggestions. I am constantly trying to improve the service and having more accesible logs is one of them.
Currently, my users do not store anywhere near a million logs for their applications, its more like hundreds to a thausend or two.



There is no practical limit on how many logs you can create, and there is no disk space limit.
The logs can be up to 10KB in size, and you can have as many of them as you want.
Everything is usage based, so as long as you have enough remaining usage, you can store logs.

Logs are kept for 1 week.




You are right, publishing this as nuget package would be the better approach, however is it the easiest approach?
The licensing system should be as easy as possible to use, even for beginners, so I tried to make it as simple as possible and let users just drop in the licensing loader into their project, set the application ID and be done for the most part.

I might create a poll in the future and just ask my users if they prefer my method, or if they would like to go the nuget way, thanks for the suggestion!

(Feb 9, 2021 08:35 AM)Shadow_Cloud Wrote:  Neat! You could always have both options available, I'm not sure they need to be mutually exclusive?  Nuget just means users have a pretty simple upgrade/downgrade path and installing a nuget package should be pretty trivial? 

(Feb 9, 2021 08:35 AM)Shadow_Cloud Wrote:  Keep it up! I have tons of questions about the setup/architecture of this behind the scenes, but not sure a public forum is the best platform, if you are interested in having a conversation, feel free to hit me up ;)

(Mar 4, 2021 04:53 AM)ucsandaasu Wrote:  i still wonder why people still try to get license systems in dotnet.. thats like offering doors for houses without a actual lock lol

(Mar 4, 2021 04:53 AM)ucsandaasu Wrote:  i still wonder why people still try to get license systems in dotnet.. thats like offering doors for houses without a actual lock lol

(Mar 4, 2021 05:01 AM)neon_light Wrote:  <snip>
since an attacker will always need a valid license to get access to your server side variables.

(Mar 4, 2021 05:23 AM)xHeaven Wrote:  Is that correct? Don't you only need a license for the first time, and simply "crack" the software with the variables you just got, so after that it would work even without a license? Didn't really look into .NET licensing systems, to be honest, so if you could explain it, that'd be great.

(Mar 4, 2021 05:23 AM)xHeaven Wrote:  Is that correct? Don't you only need a license for the first time, and simply "crack" the software with the variables you just got, so after that it would work even without a license? Didn't really look into .NET licensing systems, to be honest, so if you could explain it, that'd be great.

(Mar 4, 2021 05:26 AM)Shadow_Cloud Wrote:  The encrypted values could be time sensitive, this is a common trait with access tokens like JWT. 

Code

            SecurityTokenDescriptor tokenDescriptor = new SecurityTokenDescriptor
            {
                Subject = new ClaimsIdentity(claims),
                Expires = DateTime.UtcNow.AddMinutes(ExpiryInMinutes),
                SigningCredentials = new SigningCredentials(GetSymmetricSecurityKey(), SecurityAlgorithms.HmacSha256Signature)
            };