maidsafe-archive / beaker-plugin-safe-authenticator Goto Github PK

Operation System: Debian, Fedora
Beaker Version: 0.5.1

The Authenticator frequently does not log apps into the network. They fail with a 'could not connect to the network' message. This happens with the web hosting manager and the email app. It happens most often if other apps are open, but sometimes it happens at startup. App logfiles show bootstrapping and client whitelisting errors.

Workarounds include restarting everything, which sometimes works. More reliable is restarting the browser and revoking all permissions (including for the browser) then restarting the app.

Other apps that often (usually) fail to authenticate are listy.test, and vidy.test. These should request authentication when the user uploads new content, but often this does not occur, or rather the request is not acknowledged (i.e. there is no popup asking for permission).

We are allowed 4 instances (what's the correct word here?) 4 apps can connect to the SAFE Network.

However, if you fail to authenticate because you mistyped username/password, after you do successfully authenticate, you won't be able to get another app to communicate on SAFE. The act of attempting a login that fails, will doom your apps to non-communication until you restart the SAFE browser

To duplicate.

1. Restart the SAFE browser to start with a clean slate
2. Authenticate, but purposely mistype username or password so you get authentication error
3. Correct your username or password and go ahead and login
4. Go to safe://app.portlandspirit and watch it fail to read mutable data
5. Restart the SAFE browser to start with a clean slate
6. Carefully type username/password so you authenticate successfully the 1st time
7. Go to safe://app.portlandspirit and watch it succeed in reading mutable data
8. Repeat as necessary to convince yourself that this is because of the 1st failed authentication

I am now unable to revoke any apps.

Closing the browser and restarting does not cure the problem.

Error code : -11. Description : code error : routing interface error -> EventSenderError(EventSubset("SendError(...)"))

So, I uploaded a site while the Authenticator was shutdown. Having previously been authenticated, the Web Hosting Manager appears to retain ability to upload. safe://testtest/ then exists where I expected it to fail.

Unclear to me whether that is intended behaviour, given previous tests that seemed not to be possible. I don't know, if the Authenticator then is just a bouncer now and not perpetually confirming access.

Prompts a thought about what control the Authenticator would have after granting access - would an app be able to ignore its revoking access, if the app doesn't need the Authenticator once it's got in?

File | Show SAFE logs

Would make more sense to have newest logs on top

It is unclear which index.html file is being referred to in the installation instructions. After going through all of the build steps running find . -type f -name index.html from the root project directory returns nothing but stuff from inside node_modules.

Ok I keep getting this:

"Core error: Unexpected: Could not connect to the SAFE Network" When trying to create a new account on test net alpha 2 using the safe browser.

I'm using Windows 7