FileSystem - wheres "CreateFile"?

[Lindon]

OK so I want to use the file system , and its nice blowfish encryption to store user credentials - but of course the first time in there are no credentials, so I need to gather the users authentication data (user name and password), create the JSON file, and then encrypt it... but I cant see how I do this "Create the JSON file" in the FileSystem and File API documentation...anyone got a clue?

I know I can Loadas and DumpasJSON but thats not what i'm trying to do here as they dont have any encryption...

[d.healey]

@Lindon I think there is a function called something like writeEncryptedObject might be what you need.

[Lindon]

@d-healey said in FileSystem - wheres "CreateFile"?:

@Lindon I think there is a function called something like writeEncryptedObject might be what you need.

nope that requires I already have the file in question:

File.writeEncryptedObject(var jsonData, String key)

[Christoph Hart]

Are you sure? I think it should be possible.

[ustk]

@Lindon AFAIR the file is automatically created...

[Lindon]

@ustk @Christoph-Hart

OK can either of you give me an example? I have this JSON:

const var p =
        {
            "id": "myID",
            "password": "something"
        };

how do I encode this in a file ?

• to be precise - in a file that currently does not exist...

[Casey Kolb]

@Lindon It's what David said writeEncryptedObject

You just need a File object in HISE in which to store it. That doesn't mean the file already has to exist.

[Casey Kolb]

Try something like this:

const var p =
        {
            "id": "myID",
            "password": "something"
        };
local machineId = FileSystem.getSystemId();
local dir = FileSystem.getFolder(FileSystem.AppData);
dir.getChildFile("license.dat").writeEncryptedObject(p, machineId);

[Steve Mohican]

@Lindon
Are you using Woocommerce REST API for customer login?
Which REST API method do you suggest for this (verifying purchases, license status...etc)?

[Lindon]

@Lunacy-Audio said in FileSystem - wheres "CreateFile"?:

const var p =
{
"id": "myID",
"password": "something"
};
local machineId = FileSystem.getSystemId();
local dir = FileSystem.getFolder(FileSystem.AppData);
dir.getChildFile("license.dat").writeEncryptedObject(p, machineId);

OK thanks - now we are back at this AppData shenanigans, which I was hoping to avoid...

[Lindon]

@Steve-Mohican said in FileSystem - wheres "CreateFile"?:

@Lindon
Are you using Woocommerce REST API for customer login?
Which REST API method do you suggest for this (verifying purchases, license status...etc)?

No I am using a custom built api that checks users subscription levels and which plug-ins they have access to.

[d.healey]

@Lindon I think appData was just an example, use a different folder if you want to.

[Lindon]

@d-healey said in FileSystem - wheres "CreateFile"?:

@Lindon I think appData was just an example, use a different folder if you want to.

I didnt mean literally just "AppData" - its any folder in the file system - its a lot less friendly than the loadAsJSON, saveAsJSON, which puts the file in the {PROJECT FOLDER} when I'm in development and using HISE, and puts it in the projects own folder when its compiled...

Where as the File System insists upon using (for example) the AppData folder all the time, elsewhere I've asked why we cant have :

local dir = FileSystem.getFolder(FileSystem.ProjectFolder);

as clearly there's a mechanism at play that can resolve this in development and at run time...

[Christoph Hart]

@Lindon said in FileSystem - wheres "CreateFile"?:

local dir = FileSystem.getFolder(FileSystem.ProjectFolder);

And this folder is pointing to what in a compiled plugin?

[Lindon]

@Christoph-Hart pointing to AppData

[Casey Kolb]

@Lindon I haven't had any issues using the AppData folder both for development in HISE and in the compiled plugin. It's actually nice because you don't have two sets of the same files. For example, in my code I create and store a custom settings file in the AppData folder, so when I'm developing in HISE it just writes to the same file as the compiled plugin, which is totally fine.

Is there a specific use-case you want for saving things to the Project Folder instead of the AppData folder?