Quick-Admin-Login

It is now possible to associate a legal ID (or a Neuro-Access ID) with an administrative account on the Neuron®, from the build 2025-01-21. The login page now shows an animated QR code that you can can using the Neuro-Access app.

To associate a Neuro-Access ID (or legal ID) to a user account, edit the corresponding user. You will see three fields that have to be provided: The current Legal ID and the corresponding personal number and country code. You can get these from quicklog.in if not known.

Once the information has been provided, you can login to the administrative console of the Neuron® using the corresponding legal ID.

Updating ID

As legal identities are limited in time, there will come a point when an ID needs to be updated. This will obsolete the old ID, which will be replaced by a new one. As long as this process is followed (i.e. old ID is obsoleted) and the new ID contains the same personal number and country code you can also use the new ID to login to the same user account. The legal identity reference will be correspondingly updated, and an event will be logged, for reference.

Event Log

All administrative logins are logged to the event log, so too the logins using Neuro-Access digital identities. The message text and corresponding properties may be different. Any problems such as duplicate legal identities associeted with multiple accounts, etc., will also be displayed in the event log.

#new, #features, #neuron, #admin, #neuro-access, #quicklogin

Content-Only Service Template

A new open repository has been published that simplifies the creation of new services that only publish content-files on the TAG Neuron®. The repository also contains instructions on how to implement such a service and the different steps that need to be completed in order to create an installable package for the service, to distribute it in a Neuron® network. It also shows how to implement a service that lets users login using Neuro-Access, or the administrative interface.

For more information, see the TemplateContentOnlyPackage on GitHub.

#new, #repository, #neuron, #neuro-access

Development Neurons and Neuro-Access integration

If you are developing a local project on a locally hosted development Neuron®, and you want to integrate Neuro-Access to let users to login to show protected pages, your development Neuron® must be configured to permit this. This is done by adding the XMPP addresses (JIDs) of the apps involved during development to the Roster of the development Neuron®. On published Neurons, this is not necessary, as they are federated and use their domain names to interconnect with other Neurons (such as the Neurons serving your Neuro-Access connections). But a developer Neuron® cannot do this, as it most probably lacks both a domain name and a public IP address. Communication in this case, is done using the XMPP Addresses (JIDs) of the Neurons, as clients to their parent Neurons (which are federated). For communication to pass in this case, and not be rejected as invalid, the sender has to reside in the Neurons Roster (accessible from the Admin page, in the Communication section).

#neuron, #neuro-access, #development

Recovering Neuro-Access accounts from script

Before reading this post I would recommend having a look at the following post: obinfo URI scheme

---

When someone has lost access to their Neuro-Access account, you can provide the app with the required information for a recovery trough obinfo URIs. The following code will show you how to go about creating an obinfo URI for account recovery. Note that is is not the same as a Transfer between devices as this will invalidate any identities connected to the account

---

Get the account information

It is required to know the account name of the user

UserName:= "FooBar";
Account:=Waher.Service.IoTBroker.XmppServerModule.GetAccount(UserName);

Expiry date

Set for how long the account information will be available

Expires:= Today.AddDays(7)

Create the account info

GW:=Waher.IoTGateway.Gateway;
Data:=<Account xmlns="http://waher.se/schema/Onboarding/v1.xsd"
				userName=Account.UserName
				password=Account.Password
				domain=GW.Domain />;
Data:=Utf8Encode(str(Data));
Key:=RandomBytes(16);
IV:=RandomBytes(16);
Data:=Aes256Encrypt(Data,Key,IV);
Req:=<Info xmlns="http://waher.se/schema/Onboarding/v1.xsd" 
			base64=Base64Encode(Data)
			once=true 
			expires=Expires.ToUniversalTime() />;
OnboardingDomainName:=Waher.Service.IoTBroker.Legal.LegalComponent.GetOnboardingNeuronDomainName();
Info:=GW.XmppClient.IqSet("onboarding."+OnboardingDomainName,str(Req),10000);

Create the URI

Code:=select /default:Code/@code from Xml(Info.InnerXml);
URL:="obinfo:"+OnboardingDomainName+":"+Code+":"+Base64Encode(Key)+":"+Base64Encode(IV);

#neuro-access

Neuro Access 2.0 Android Release

---

Neuro Access 2.0 has been officially released on the Google Play Store. Currently, on the app, you can:

• Create an account
• Apply for an identity
• Use it as a form of authentication (for example, you can log in to this community site)

The app is a replacement for the TAG ID app

• If you have an Android device, you can download it here.
• For iOS users, the app will be released as soon as possible.

Note: The store page, at the time of writing, has not had its images updated to represent the new app.

---

#neuro-access, #app, #id