Grant Update [BIF-003] Factom into Alfresco Content Apps / Developer Framework

Niels Klomp

BI Foundation
Core Committee
Governance Working Group
Update 1:


After waiting on resources to become available BIF has finished the actual coding of the Factom integration into Alfresco ADF for some time now. We hit some snags because of updates to the ADF framework during development. We are currently finishing up some documentation work for both developers and system administrators on how to deploy the solution into Alfresco, as well as do some deployment testing to allow for easy deployment on Amazon AWS.


The below screenshots shows the added menu items for interactive registration and verification and the verification window when invoked on a file.


A Dutch company that wants to develop Alfresco based portals for governments already has expressed interest in this solution. We hope more clients and software vendors will follow.


The next update will be the delivery of the final solution, source-code including documentation. We expect that to be before the end of May 2019.
 

Attachments

mboender

BI Foundation
The main work on this has been finished. It is in use by some of our partners.

This and upcoming sprints have some stories on them to further “productize” the offering. Things like Documentation and Samples and creating a public Alfresco OSS repro.
 

Tor Paulsen

The Factoid Authority
The main work on this has been finished. It is in use by some of our partners.

This and upcoming sprints have some stories on them to further “productize” the offering. Things like Documentation and Samples and creating a public Alfresco OSS repro.
Thank you - Can you confirm that the work as described in the grant application is now deemed complete by you?
 

Anton Ilzheev

De Facto
Exchange Working Group
Core Committee
Website Committee
@mboender can you post a link to repo, so community can use it?

The main work on this has been finished. It is in use by some of our partners.

This and upcoming sprints have some stories on them to further “productize” the offering. Things like Documentation and Samples and creating a public Alfresco OSS repro.
 

Matthias Fortin

HashnStore
Following discussions between Anton and Niels in fct market channel, an update would clarify the situation. Do you intend to publish this work as soon as possible or are you waiting for the DID integration grant to be completed too?
 
Last edited:

mboender

BI Foundation
Hi Anton, Tor and Matthias.

First of all, sorry for the delayed response.

We still have to do some refactoring work together with documentation work based on the feedback we have from our customer and partners.
And as you probably know we are working on integrating DIDs (including DID-auth) with Alfresco right now. As we believe that work to be more important at this stage, we have given it priority over the refactor work.

Obviously we are 100% committed to providing the Alfresco integration, but we really would like to keep the order as we have done now. Meaning providing the DID integration to the community, together with the refactor work and documentation, to get a complete solution of Alfresco, DIDs and Factom.
 

Niels Klomp

BI Foundation
Core Committee
Governance Working Group
Short answer in 4 weeks. We are more than aware this grant is taking too long. Here is the back story:


Early 2019 we had a basic Alfresco developer framework specialization using factom-js. The problem there was that we were working against a complete new product of Alfresco, which didn’t allow for an easy modulair approach. Then there was the problem of using the ECs from the client, as it needed secure browser storage.

A lot of rework was done, where we decided to move the Factom integration into a backend agent instead of doing it directly from the browser as that would require a secure key-storage. This backend agent was published in April/May in our open-source repositories (https://github.com/Sphereon-Opensource/alfresco-blockchain-agent) (update 1 above).

We also modularized more of the code, separating the parts from the ADF, as well as updating it to later versions of ADF as it became a bit more mature. We have one partner using the integration into their development, which is about creating Alfresco Portals for government agencies. As they are Alfresco developers this partner is able to integrate it themselves rather easily. For other parties it remained way too technical to easily do it. So basically the components were (are) there, but it is too many moving parts and too much manual work to get it all up and running.


To give you a bit of an example why this certainly isn’t productized, look at the documentation:
https://sphereon.atlassian.net/wiki...4533/Sphereon+Alfresco+blockchain+integration


So we had to incorporate feedback from a Alfresco development partner and still had productization, which includes documentation and a bit of refactor/modularizing work to do. At the same time we started working on DID-auth for Triall. The scope of that project grew much bigger than initially envisioned (also the scope of what we will be delivering to the Factom community grew significantly; see the DID-auth thread for that). We decided to bring the DID-auth work with bigger scope together with the Factom integration at the same time as that makes the most time for both our developers as well as the recipients (community)


We are working on this. Actually our tech lead is directly working on it himself most of his time, hoping to show you that we do take this rather seriously. At the same time we are working on DID-auth. All together we have 4 people working on both projects and we expect to bring both DID-auth and Factom integration into Alfresco in 4 weeks time from now. If we do not get the DID-auth work done by then, we will release the Factom integration into Alfresco separately.


(PS. The Off-blocks Alfresco integration is something different from the above)
 

Niels Klomp

BI Foundation
Core Committee
Governance Working Group
This Off-Blocks integration is mainly to access files from and to Alfresco from Off-Blocks. So from Alfresco/Sharepoint you are able to send out files to be signed, as well as return/store them on Alfresco.

Furthermore Off-Blocks has a more elaborate signing scheme allowing multiple versions to be linked etc. This integration is not much more than creating hashes and signatures on a single chain.

Since it is open-source with permissive license nothing is stopping people or us from making more elaborate solutions of course. I certainly see that happening when the generic signature specification gets adopted/ratified.
 

Niels Klomp

BI Foundation
Core Committee
Governance Working Group
BTW the Sphereon store part (and thus our API integration) in the above PDF of course is not applicable for the open-source integration ;)
 

Niels Klomp

BI Foundation
Core Committee
Governance Working Group
The refactoring of the agent is completed. The agent was not part of the initial scope of this grant to begin with. The agent basically allows signing and verifications in the background as a component in the kubernetes cluster for Alfresco. The scope of this grant was to only allow direct interactive functions and not have an agent like background integration.

So very much like our supported commercial integration, the open-source integration contains that functionality. We removed the javascript only frontend integration with the agent approach like we have done in our commercial offering.

It can work with factomd and optionally with facom-walletd, dependent on whether you use a private or public EC address in the configuration. We still need some work on the frontend, although everything works from the Platform and Share (Alfresco UI) side and we need to add a signature to the open-source version in the entry. Of course the code is tested

The different agents and it's source code can be found at
https://github.com/Sphereon-Opensource/alfresco-blockchain-agent
https://github.com/Sphereon-Opensource/alfresco-blockchain-agent/blob/master/README.md
https://github.com/Sphereon-Opensource/alfresco-blockchain-agent/tree/master/blockchain-agent-factom

The models for Alfresco and starting point for documentation on GH pages:
https://sphereon-opensource.github.io/alfresco-blockchain-integration/


We need to add the signature and do a bit of frontend work and then tag the first release of the software.
The next version will contain in-person signing instead of company seals (outside of the grant scope, just to give a heads up on future functionality).
 

Niels Klomp

BI Foundation
Core Committee
Governance Working Group
Please follow the documentation and the specific repos where it is explained. If you need help you can ask.

Not part of this grant and solution, but part of the future total package for Alfresco. We are having some issues with CAS itself for the DID-auth integration. Our senior devops engineer spent the better part of a week on it already and we are getting in contact with Alfreco itself about it. The steps for Cas itself will be documented as well of course.
 
Top