ID Austria under e/OS possible?

Hiya,

is it possible to run ID Austria on e/OS? My banking app is supported, according to a list but will ID Austria work as well?

Thanks

Regain your privacy! Adopt /e/OS the deGoogled mobile OS and online servicesphone

At least the app ‘Digitales Amt’ seems to work (eOS 2.9-t, FP5)
But I havn’t set up ID Austria yet.

Same here. “Digitales Amt” including the login via ID Austria works fine on a FP4 with the current eOS (2.9).
I don’t use a dedicated “ID Austria” app though (and couldn’t find a dedicated app)

2 Likes

Thanks for your replies!

Bad wording on my end, Digitales Amt is that what I wanted to ask about :slight_smile:

2 Likes

Same here, Digitales Amt works with on my FP3 with the current eOS v2.9 :+1:

1 Like

I own the FP3 with /e/os and ID Austria is working - but I can’t get “eAusweise” to work. As soon as I try to connect eAusweise with ID Austria - the app opens the browser and tries to connect - but it should open the app. So, this is not working.

I also own the FP5 with stock Android 14 and ID Austria and eAusweise is working.

Now I bought the murena FP6 with e/os/ and ID Austria is not working - as soon as I try to connect, I get an error message

1 Like

Same here

I ll contact id Austria now

1 Like

I will do the same Thx

Any luck contacting them? I bought the FP6 today and updated to E/OS and get an error activating the app

1 Like

I will wait for the next update, version 3.0.4. If it doesn’t work, I will call again.

In my opinion, the biggest problem is that the ‘Ausweis’ app doesn’t recognise that the ‘id Austria’ app is already installed. On my FP3, ID Austria is working, but Ausweis is not.

Same error, after updating to 3.0.4.
I got just the respond “we are having more Tickets at the moment, please be patient”

Same for me update to 3.0.4 did not fix it.

I went though the logcat and the only logs that seem related are:

07-18 22:39:41.419   785   785 I servicemanager: Caller(pid=964,uid=1017,sid=u:r:keystore:s0) Found android.hardware.security.keymint.IRemotelyProvisionedComponent/default in device VINTF manifest.
07-18 22:39:41.413  2281  3085 I RemoteProvisionSysSvc: getRegistration(android.hardware.security.keymint.IRemotelyProvisionedComponent/default)
07-18 22:39:41.423  2281  2281 I RegistrationProxy: onServiceConnected: com.android.rkpdapp.service.RemoteProvisioningService
07-18 22:39:41.425  2281  2300 I RegistrationProxy: IGetRegistrationCallback.onError:RKP is disabled. System configured with no default URL.
07-18 22:39:41.429   964   976 E keystore2: system/security/keystore2/rkpd_client/src/lib.rs:133 - IGetRegistrationCallback failed: 'android.os.RemoteException: RKP is disabled. System configured with no default URL.'
07-18 22:39:41.429   964   975 W keystore2: system/security/keystore2/src/remote_provisioning.rs:97 - Error occurred: system/security/keystore2/rkpd_client/src/lib.rs:233: Trying to get to IRegistration service.
07-18 22:39:41.429   964   975 W keystore2: 
07-18 22:39:41.429   964   975 W keystore2: Caused by:
07-18 22:39:41.429   964   975 W keystore2:     0: system/security/keystore2/rkpd_client/src/lib.rs:136: GetRegistrationCallback failed: "android.os.RemoteException: RKP is disabled. System configured with no default URL."
07-18 22:39:41.429   964   975 W keystore2:     1: Failed to get registration
07-18 22:39:41.488   905   905 E KeymasterUtils: IKMHal_sendCmd failed with rsp_header->status: -49
07-18 22:39:41.488   905   905 E KeyMasterHalDevice: keymint_generate_key
07-18 22:39:41.489   905   905 E KeyMasterHalDevice: ret: -49
07-18 22:39:41.489   964   975 E keystore2: system/security/keystore2/src/error.rs:183 - system/security/keystore2/src/security_level.rs:680
07-18 22:39:41.489   964   975 E keystore2: 
07-18 22:39:41.489   964   975 E keystore2: Caused by:
07-18 22:39:41.489   964   975 E keystore2:     0: system/security/keystore2/src/security_level.rs:674: 
                                While generating without a provided attestation key and params:
                                    [KeyParameter { tag: r#KEY_SIZE, value: Integer(256) },
                                    KeyParameter { tag: r#ALGORITHM, value: Algorithm(r#EC) }, 
                                    KeyParameter { tag: r#EC_CURVE, value: EcCurve(r#P_256) },
                                    KeyParameter { tag: r#PURPOSE, value: KeyPurpose(r#SIGN) },
                                    KeyParameter { tag: r#PURPOSE, value: KeyPurpose(r#VERIFY) },
                                    KeyParameter { tag: r#DIGEST, value: Digest(r#SHA_2_256) }, 
                                    KeyParameter { tag: r#USER_SECURE_ID, value: LongInteger(6286511603326242745) },
                                    KeyParameter { tag: r#USER_AUTH_TYPE, value: HardwareAuthenticatorType(3) },
                                    KeyParameter { tag: r#CERTIFICATE_NOT_AFTER, value: DateTime(2461449600000) },
                                    KeyParameter { tag: r#CERTIFICATE_NOT_BEFORE, value: DateTime(0) },
                                    KeyParameter { tag: r#CERTIFICATE_SERIAL, value: Blob([1]) },
                                    KeyParameter { tag: r#CERTIFICATE_SUBJECT, value: Blob([48, 31, 49, 29, 48, 27, 6, 3, 85, 4, 3, 19, 20, 65, 110, 100, 114, 111, 105, 100, 32, 75, 101, 121, 115, 116, 111, 114, 101, 32, 75, 101, 121]) },
                                    KeyParameter { tag: r#ATTESTATION_CHALLENGE, value: Blob([227, 70, 78, 53, 39, 202, 18, 143, 76, 152, 89, 21, 223, 186, 20, 210, 230, 130, 154, 111, 183, 23, 152, 129, 44, 150, 67, 24, 78, 159, 32, 163]) },
                                    KeyParameter { tag: r#CREATION_DATETIME, value: DateTime(1752871181429) },
                                    KeyParameter { tag: r#ATTESTATION_APPLICATION_ID, value: Blob([48, 60, 49, 22, 48, 20, 4, 12, 97, 116, 46, 103, 118, 46, 111, 101, 46, 97, 112, 112, 2, 4, 120, 179, 248, 151, 49, 34, 4, 32, 141, 172, 60, 108, 229, 167, 123, 188, 183, 7, 143, 161, 48, 126, 4, 35, 169, 152, 233, 113, 240, 31, 67, 182, 19, 141, 210, 231, 100, 211, 223, 253]) }].
07-18 22:39:41.489   964   975 E keystore2:     1: Error::Km(r#SECURE_HW_COMMUNICATION_FAILED)

@cad-forge For me on FP6 the Ausweis App correctly detects if ID Austria is installed (even though it doesn’t work), but by default a browser is opened when trying to connect it, which can be fixes by manually enabling all the URL handlers in the Android settings of the ID Austria App.

This topic was automatically closed after 90 days. New replies are no longer allowed.

So, finally my update / status report

ID Austria v5.0.0 (2025060503) on FP5, eOS 3.0.4-t/A13
Important: not rooted, bootloader locked

  • Installation of app & online pre-registration → no problem
  • Finalisation of registration (in-person at an authority office) went ok, But app would not immediately connect/authenticate to the service. Rather due to unavailability of the service server-side, not as problem of the app/device/eOS
    Had to be repeated later via PC, similar to pre-registration generating again a QR code to register app/device to the service → success
  • Since that, everything works (with app-tracker enabled, doesn’t detect any tracker)
  • First tests so far with FinanzOnline, VBV, Sozialversicherung → no issues
    2FA: User/PW plus Fingerprint
  • Not tested yet:
    – other SSO logins / authentifications with private companies
    – digital signatur on pdf
    – use of app via VPN
    – EU-Login (not implemented yet?)
2 Likes

Perhaps of interest 


For me on FP6 pin only doesn’t work either.

with the new 3.1.2 - ID Austria is working.
With eAusweise App, it is the same. As soon as I want to connect eAusweise with ID Austria, not the app but a browser is opening.

I saw the workaround, but I don’t know how to do this.

@cad-forge This is what I did:

Open Settings
Search for eAusweise and open the settings for it
Click on Open by Default
Make sure open in App is selected
Click add Link below Links to open in app
Select all the links

With this workaround it is now working on 3.1.2 on FP6

1 Like