I'm wondering what version(s) of the SMB protocol that spring-integration-smb extension is currently supporting. I understand that Microsoft will be deprecating SMB1 soon (or already) and that only SMB2 and/or SMB3 will be supported in Windows Server. Does spring-integration-smb support SMB2/SMB3 protocol today?
I've been reviewing the spring-integration-smb and jcifs code base but I haven't been able to find this answer yet.
Currently the Spring Integration SMB extension is based on the `compile "org.codelibs:jcifs:1.3.18.3" and according some resources in the Internet it support only SMB1: Smb version 2 upgrade issues
However according the latest news of that project, we are good to tackle their new version with announced SMB2 and SMB3 support: https://github.com/codelibs/jcifs
Feel, free to raise an issue in GitHub project and we also are open to accept a contribution on the matter.
In case SMB3 is required there is also a commercial option that supports all SMB dialects named jNQ developed by Visuality Systems.
Related
Amazon recently published its Amazon Product Advertising API v5.0 for Amazon Affiliate Program. From 31st October 2019, previous version 4.0 of API will be taken down and only v5.0 will be supported to access Amazon products programmatically.
With these changes, most available node modules and applications will no longer work with V5.0. For this Amazon PA-API 5.0, Amazon has released an SDK for PHP, NodeJs, Python and, Java. However, using the SDK for NodeJs may require time to configure.
That being said, is there an available Node Package module that we can use to easily start integrating our application?
There are a few NPM wrappers that are available today that help you use Paapi 5.0 for NodeJS. All of this module uses the amazon SDK for their code.
amazon-paapi - By far my favorite as it uses simple to understand node syntax. Adding parameters is much like how you do it using amazon scratchpad. It also support custom parameter options.
amazon-pa-api50 - Another great module. However, as of this writing, I found some limitations on optional parameters you can add to some operations.
apaw - alternative option.
Is there any way to do user authentication without any third-party tools; just need to prevent access with username and password.
Yes it is possible and you can use X-Pack, which is an Elastic Stack extension that provides security. By default, when you install Elasticsearch, X-Pack is installed with a 30-day trial.
here the docs: https://www.elastic.co/guide/en/elasticsearch/reference/current/configuring-security.html
If you are looking for something open-source opendistro for elasticsearch provides the same services for free and has support for Active Directory, LDAP, Kerberos, SAML, and OpenID Connect, here the docs: https://opendistro.github.io/for-elasticsearch-docs/docs/security-configuration/
If you wish you can install the OSS version of elasticsearch, which includes only Apache 2.0 licensed code (here: https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-oss-7.6.1-linux-x86_64.tar.gz) and then install the standalone plugin for security with this command:
`sudo bin/elasticsearch-plugin install https://d3g5vo6xdbdb9a.cloudfront.net/downloads/elasticsearch-plugins/opendistro-security/opendistro_security-`1.4.0.0.zip
as described here:
https://opendistro.github.io/for-elasticsearch-docs/docs/install/plugins/#security
Let me know if you need help for configure authentication!
Good luck!
The basic auth part if free starting from Elasticsearch 6.8. However, you'll need to buy X-Pack for advanced stuff like LDAP Authn / Authz.
https://www.elastic.co/blog/security-for-elasticsearch-is-now-free
I have a requirement to upload the image pdf file/files to IBM File Net using Express.JS! How to do it?
I'm a new bee for File Net, even I'm not able to find sufficient docs for the same.
Any help will much be appreciated.
You are out of look as FileNet does not come with suitable APIs out-of-the box.
tl;dr: You have the following options:
Develop a custom service
Install and use the optional CMIS API
Install and use the optional GraphQL API (only if you are on FileNet version >= 5.5.4)
You may ask if installing and configuring the IBM ECM CMIS for Enterprise Content Management would be an option. That would allow you to use CmisJS.
With FileNet 5.5.4 they introduced an optional Content Services GraphQL API
As an alternative, you or somebody else with FileNet experience needs to develop a custom REST/Web-Service for uploading files.
We are getting connection reset error when we are trying to connect to windows share using spring integration smb. We observed that we are getting this when we disabled smb1 in windows share.
Is there any way to know which smb version spring smb api's using or is there any way available to developer to select the version ( say smb1 or smb2 ) while making connection.
Please help
Spring-integration-smb uses JCifs which only supports SMBv1. It shouldn't be too hard to build a new Spring Integration connector which leverages SMBJ to support SMBv2.
I am looking for an Opensource lightweight IAM to be used in development as a substitute for the real commercial IAM in production. Something with basic IAM functionalities, easy to install & easily configured to inject HTTP headers like user group.
Is OpenAM a good option? Any recommendations?
OpenAM comes from a very good pedigree...is forked from OpenSSO which is open-sourced code from the original SUN Access Manager product. OpenSSO was abandoned by Oracle after the Sun acquisition, so another company took it over and promoted a developer community around it.
Overall its a good choice for your requirements; that is:
Production-ready - yes, this version and previous versions have been used in production implementations
basic IAM functionality - it contains basic web access management functions and more than a few advanced features.
Inject HTTP headers - Yes, this is a standard function among web access management products.
In the past, a limitation with OpenAM/OpenSSO is that it required Sun Directory as the configuration store; however, this has changed with recent releases allowing other directories to be used.
Expect that installation and configuration of OpenAM to be rather command-line intensive; that is, with a minimal package installation and then options set in config files or thru utilities.
Hope that helps...