FTP-server | FTP server & client based on C | FTP library

Solved. The solution was to generate new rsa and dsa keys with:

You need to reference the specific value in the exported resource attribute object. The error message states:

azurerm_storage_share.jms-sftp-share is object with 3 attributes

indicating you need to reference the specific element in the object. The three attributes are denoted with the one two and three Strings you use as keys to iterate over in the question. You then access the specific element like:

in case I stop the sshd on Win10 and start it not as a service, just with c:>sshd.exe

• In one case, sshd is run as a service, possibly with the LocalSystem account
• In the other, from comand-line, you are running sshd as you (your Windows account).

The environment would not be the same, especially for the "authorized_keys" file.
As mentioned in the documentation:

In Windows, sshd reads configuration data from %programdata%\ssh\sshd_config by default, or a different configuration file may be specified by launching sshd.exe with the -f parameter.
If the file is absent, sshd generates one with the default configuration when the service is started.

Activate the logs when running the ssh daemon as a Windows service, as seen here:

Open an admin powershell prompt and run:

Indeed, the SFTP protocol does not have a way to provide a list of files matching any criteria. It does not matter, what SFTP library you are using.

You would have to use another interface/API if you need the filtered list. If you have a shell access, you might use shell command ls *.zip.

Or build you own (REST?) API.

If your app is fully static you can build it into static js files (i.e. npm run build in vue.js) and then it should work on ftp hosting. Note, however, that in this case if your usage is low you can use something like Google App Engine or Netlify and essentially get free hosting for your static app.

However, if your app involves some back-end operations, i.e. express.js then you need to be able to run node.js server itself and you need a VPS-based or container-based hosting.

Feel free to reach out to me via discord here and ask more questions - https://discord.gg/UTxjBf9juQ.

After some time I figured out a solution in a stepwise-learning Process:

Step 1: Retrieving all subdirectories

First I needed to get all directories the files are stored in. Given the assumption that all relevant directories are subdirectories of \IN, my solution was to get the String-return for that information and iterate over the splitted `String.

SFTP is a binary protocol, defined by IETF standard draft. Latest version can be found on IETF website: https://tools.ietf.org/html/draft-ietf-secsh-filexfer-13, but make sure it's what your server supports.

As it's a binary protocol, you would need a specialized client program to use it.

This question is indeed about different integration options. In general, it is one or more Application Entities (AE) that operate with the resources / data in a CSE. Every tool, application, protocol gateway, or "adaptor" is, from oneM2M perspective, an AE.

A special form of AE is the IPE, the Interworking Proxy Entity. It is used to connected another system or infrastructure to a CSE and mediate between these two worlds. The CSE part, ie. the protocol and the data formats etc, are covered by the oneM2M specification, and the other part must then implement the other protocol and technical specifications. The actual task is then to convert the data and expected behaviour between both worlds.

I am not sure from your description whether what you are planning is such a protocol "gateways", or just push the data received via an ftp server to a CSE. But technically, this doesn't matter much for the oneM2M part: You need to define how the data is structured on the CSE etc anyway.

For the data retrieval: As you mention in your question there is a third option to the other two:

1. The AE monitors an external system for new or updated resources, and pushes them to the CSE as soon as when they are ready.

From oneM2M's perspective this is completely fine. Technically you must make sure how to find out when the data is new, completely received, still valid, etc. ... basically all the challenges when you are polling resources. The first two options would be more helpful because you would avoid some of the problems that come with polling, but as you wrote sometimes you just don't have control about the system you want to connect to.

I was able to upload a file with your code. It was working like a charm. So, there is no error in your source code. I used the Microsoft.NET.Sdk.BlazorWebAssembly SDK with net5.0 as the target framework. Probably, it's a configuration issue with the storage account.

The CORS policy allows the host of the application (https://localhost:5001) to accesses the resources with any verb and any header (*) values. The response can include the content-length header. Is your WASM self hosted or hosted within an ASP core application? You can easily spot what origin is sent to azure by inspected the request.

Based on your context, only a few verbs like PUT might be enough.

The configuration of the SAS key can also be more specific.

Using SAS from Blazor WASM

Even not entirely part of your questions, but worth mentioning. If you want to allow a direct upload into your blob storage - and there are good reasons for it - before uploading a file, your WASM app should send a request to your API, the response contains the SAS key that can only be used for this one operation. The SAS key itself should be a user delegation SAS key