This package provides a firebase integration in to cone.app.
Installation
Include cone.firebase to install dependencies in your application’s setup.py.
Configuration
Adopt your application config ini file to define firebase related API keys.
[app:my_app]
use = egg:cone.app#main
cone.plugins =
cone.firebase
cone.authenticator = firebase
firebase.web_api_key = xxx
firebase.service_account_json_file = path/to/service_account.json
also in your ugm.xml you can optionally add the firebase_user checkbox:
<users_form_attrmap>
...
<elem>
<key>firebase_user</key>
<value>Firebase User</value>
</elem>
</users_form_attrmap>
When you want to upgrade an existing user to FB, you can do this by checking firebase_user in the user edit form, butt attention: you have to manually enter the password since the firebase API expects the password in cleartext.
Contributors
Robert Niederreiter
Phil Auersperg
Changes
1.1.2 (2026-10-31)
Sort the imports with ruff (one per line, from imports first, no sections) and format the code with ruff format (90 characters per line, single quotes). [rnix]
Add import sorting (I rules) and the formatter settings to the ruff configuration in pyproject.toml. [rnix]
1.1.1 (2026-10-24)
Do not log the password if encoding the login data fails. [rnix]
Register the user event handlers by calling classhandler.handler. Used as decorator it returns itself, so on_user_created, on_user_modified and on_user_deleted were bound to zope.event.classhandler.handler and calling them directly silently did nothing. [rnix]
unregister_device_token_for_user does nothing for an unknown login, register_device_token_for_user raises a KeyError naming the login. Resolving the user for a login is no longer repeated in three functions. [rnix]
cone.firebase.testing: The fake firebase_admin follows the API of firebase_admin.auth. create_user takes uid, user functions return a UserRecord and raise UserNotFoundError for an unknown user. FirebaseLayer also patches management.auth, restores everything it patches and removes only its own event handlers on tear down. [rnix]
Remove unused imports and variables ruff flags. on_user_deleted keeps the auth.get_user call, it raises UserNotFoundError for an unknown user. Remove the broken Message.__str__ from the fake firebase_admin in cone.firebase.testing. [rnix]
Use logger.warning instead of the deprecated logger.warn. [rnix]
Modernise the code ruff flags as outdated: class X(object), typing.Dict/List/Tuple over builtins, redundant open() mode. Behaviour unchanged. super(Class, self) is kept, see cone.app. [rnix]
Pin the ruff rule selection in pyproject.toml. [rnix]
Pin setuptools<82.0.0 in mx.ini. pyramid 2.0.2 still imports pkg_resources, which setuptools 82 removed. [rnix]
1.1.0 (2026-02-03)
Refactor package layout to use pyproject.toml and implicit namespace packages. [rnix]
Initial. [rnix, zworkb]
License
Copyright (c) 2021, BlueDynamics Alliance, Austria Copyright (c) 2021-2025, Cone Contributors All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Metadata
Release files for cone.firebase 1.1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| cone_firebase-1.1.2.tar.gz | 15.6 kB | Without provenance | Details for cone_firebase-1.1.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cone_firebase-1.1.2-py3-none-any.whl | Python 3 | none | any | Details for cone_firebase-1.1.2-py3-none-any.whl |
Total release size: 33.8 kB
Release files / cone_firebase-1.1.2.tar.gz
| Download URL | cone_firebase-1.1.2.tar.gz |
|---|---|
| Size | 15.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ad770aaa0793bb452abdf546f95eaabbd735cd3cb0f61c9146fe6b4c54556e06
|
|
BLAKE2b-256 checksum How to use checksums |
d3a9fa0bb198175a6fdaeb120d8e58e2d0773de50d61b91378be47376e99643f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.2
|
Release files / cone_firebase-1.1.2-py3-none-any.whl
| Download URL | cone_firebase-1.1.2-py3-none-any.whl |
|---|---|
| Size | 18.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
feda14e74f855a3e76cab52ee27f60222834a11dda0e2cae7fd3e7bfc21955f6
|
|
BLAKE2b-256 checksum How to use checksums |
0b41875d82965a82323168fa7e3c2fa2d8993612e4dd7897df83ce6921827a50
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.2
|
Security for cone.firebase 1.1.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.