MaidSafe Dev Update - February 9, 2017

This comment on the last commit suggest they removed the authenticator from the browser. Maybe they found some last minute bug or something.

Revert “SAFE Authenticator plugin integration”

1 Like

Good call. Was safe_browser with beaker-plugin-safe-authenticator only meant to be used for Test12b?

Can’t say, maybe. We should be fixed on monday anyway when they get back to work.

OK, I’ve managed to build SAFE Browser and SAFE App Nodejs now but safe-auth://home just brings up a message:
This site would like to open a URL in another program
Clicking on Allow doesn’t seem to do anything, certainly nothing like the screenshot at the top of this thread.

How do I integrate the authenticator with the SAFE browser build, or am I barking up the wrong tree?

EDIT: I’m running user_network_12_b by the way

1 Like

Hi @hunterlester, please follow the steps from to building beaker-plugin-safe-authenticator. It is clearly mentioned to add index.js file and dist folder into safe_browser/app/node_modules/beaker-plugin-safe-authenticator folder.


Sorry for the slow response. The intention is that any new CEPs would be posted in Request For Proposal within the Development category of the forum, however, it is likely that this would be discussed in a main forum thread first prior to posting. Just in case you hadn’t seen it yet, the CEP process is detailed in this thread.

I do like the idea of the mentorship program, we get approached regularly about internships, unfortunately we don’t have the resources to deliver this just yet, but as we are constantly working on recruitment I hope that this will change in the near future. Thanks for your ongoing involvement and continued interest!


Sorry for the spam, if any of you still have the log files from test-12b, can you please check this thread and see if you get a match please. Just to help debug one of the issues from test-12b


Dude do not worry about it at all!!! For us this is not spam but a call to arms. We’re here to fight with and for you all whatever little we can. :sunglasses: :innocent:


@Viv, I have my log, but that 163 post thread you linked to, has eluded my quick search to see what string that it is you want me to search for.

What should we be grepping?

If you can grep/find theese references then it’s good for us to grab from you if that’s Ok.

1 Like

Done, but search for both strings struck out for my Node. Sorry


Windows users:

I’ve got an executable bundled here for SAFE Browser integrated with beaker-plugin-safe-authenticator:

Upon entering safe-auth://home into the browser, I’m able to create an account and/or login.

Now I’m running tests with safe_app_nodejs and I want to see what other users are running into.


Alpha 1??? 20 chars bla bla bla

1 Like

WooHoo!! Bravo @hunterlester . I knew you could get it done! Definitely really helpful to us! :relaxed:


Woo! Now all we need is a network to log in to run it on :slight_smile:


I’m not quite sure, I have to look into it. I thought compiling with use-mock-routing defaults to Alpha 1 although it wouldn’t recognize my login, I had to create new account.

@JPL Are you able to create new account?

1 Like

Yes I created a new account and got to this screen. Tried the Demo App but no joy there.


Thanks so much for taking the time to compile this in an easy to install format for us non-tech maid followers!! Appreciate all of the hard work.

I was successfully able to download and started. I created a new account since I wasn’t able to log in with my previous credentials. For some reason when I tried the websites I had tried previously, I was not able to open it (e.g. safe://hello ). I may be doing something wrong, but appreciate all of the hard work!


This is good feedback for me. I need to search further into what my bundle is actually connecting to and how exactly it’s listening for calls. I’ll update asap.