eloquent-model-encrypt issueshttps://git.customd.com/composer/eloquent-model-encrypt/-/issues2022-08-23T14:17:41+12:00https://git.customd.com/composer/eloquent-model-encrypt/-/issues/4[Feature] - Api token Storage Ability2022-08-23T14:17:41+12:00Craig Smith[Feature] - Api token Storage AbilityAdd ability to store tokens with decryption of the pemAdd ability to store tokens with decryption of the pemCraig SmithCraig Smithhttps://git.customd.com/composer/eloquent-model-encrypt/-/issues/3Cannot update column attributes on encrypted column2022-08-23T14:17:00+12:00Josh SmithCannot update column attributes on encrypted columnWhen attempting to change an encrypted column attribute to nullable using `$table->encrypted('payment_number')->nullable()->change();` I received the following:
```
Unknown column type "encrypted" requested. Any Doctrine type that you u...When attempting to change an encrypted column attribute to nullable using `$table->encrypted('payment_number')->nullable()->change();` I received the following:
```
Unknown column type "encrypted" requested. Any Doctrine type that you use has to be registered with \Doctrine\DBAL\Types\Type::addType(). You can get a list of all the known types with \Doctrine\DBAL\Types\Type::getTypesMap(). If this error occurs during database introspection then you might have forgotten to register all database types for a Doctrine Type. Use AbstractPlatform#registerDoctrineTypeMapping() or have your custom types implement Type#getMappedDatabaseTypes(). If the type name is empty you might have a problem with the cache or forgot some mapping information.
```
The workaround is to the the `binary` type for now.https://git.customd.com/composer/eloquent-model-encrypt/-/issues/2Follow-up from "feat: Lara 9 / php 8"2022-06-11T09:56:34+12:00Craig SmithFollow-up from "feat: Lara 9 / php 8"The following discussion from !12 should be addressed:
- [ ] @sam started a [discussion](https://git.customd.com/composer/eloquent-model-encrypt/-/merge_requests/12#note_111435):
> Since this is a major version, we should consider...The following discussion from !12 should be addressed:
- [ ] @sam started a [discussion](https://git.customd.com/composer/eloquent-model-encrypt/-/merge_requests/12#note_111435):
> Since this is a major version, we should consider taking the opportunity to correct the naming of this field from `rsa_key_id` to `keypair_id` (and using keypair, or asymmetric key where appropriate). Reason being is that `RSA` is only _one_ of the asymmetric key algorithms that can be used with this library.
>
> In fact we should consider using ed25519 instead of rsa-2048 as it's as secure, more performant, and has smaller keys.