# Write-only fields with ActiveRecord

**URL:** <https://discuss.rubyonrails.org/t/write-only-fields-with-activerecord/89349>\
**Category:** rubyonrails-talk\
**Tags:** activerecord\
**Created:** [June 6, 2025, 12:34pm UTC](https://discuss.rubyonrails.org/t/write-only-fields-with-activerecord/89349 "2025-06-06T12:34:58Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![schmijos](https://sea2.discourse-cdn.com/rubyonrails/user_avatar/discuss.rubyonrails.org/schmijos/32/1623_2.png) [@schmijos](https://discuss.rubyonrails.org/u/schmijos)\
**Post date:** [June 6, 2025, 12:34pm UTC](https://discuss.rubyonrails.org/t/write-only-fields-with-activerecord/89349/1 "2025-06-06T12:34:58Z")

</div>

I made a custom `ActiveModel::Type` to encrypt a field before it goes to the database. The context is that multiple apps use the same database. Some write to it, some read from it. Now my side is write-only. I should never read the field, neither can I decrypt it.

How do we handle write-only fields with ActiveRecord?

- Should I raise?
- Should I return `nil`?
- Should I return the ciphertext stored in the database?
- Is an `ActiveModel::Type` not made for this? e.g. [Devise](https://github.com/heartcombo/devise/blob/cf93de390a29654620fdf7ac07b4794eb95171d0/lib/devise/models/database_authenticatable.rb#L65-L68) doesn’t use it.
- What do other people do?

This is my sketch. It raises:

```rb
class RsaEncryptedType < ActiveModel::Type::String
  def initialize(public_key: nil, private_key: nil)
    raise "At least public_key or private_key must be present" unless public_key.present? || private_key.present?

    @private_key = OpenSSL::PKey::RSA.new(private_key) if private_key.present?
    @public_key = OpenSSL::PKey::RSA.new(public_key) if public_key.present?
  end

  def type
    :rsa_encrypted
  end

  def serialize(value)
    return nil if value.blank?
    raise "Cannot encrypt. Public key missing." if @public_key.nil?

    ciphertext = @public_key.public_encrypt(value.to_s)
    Base64.strict_encode64(ciphertext)
  end

  def deserialize(value)
    return nil if value.blank?
    raise "Cannot decrypt. Private key missing." if @private_key.nil?

    ciphertext = Base64.decode64(value)
    @private_key.private_decrypt(ciphertext)
  end
end

```

---

<div class="post-metadata">

**Author:** ![tmaier](https://sea2.discourse-cdn.com/rubyonrails/user_avatar/discuss.rubyonrails.org/tmaier/32/9179_2.png) [@tmaier](https://discuss.rubyonrails.org/u/tmaier)\
**Post date:** [June 7, 2025, 9:29pm UTC](https://discuss.rubyonrails.org/t/write-only-fields-with-activerecord/89349/2 "2025-06-07T21:29:12Z")

</div>

I think you could add the following method to your model to make it read only:

def readonly? true end

---

<div class="post-metadata">

**Author:** ![ahmad54](https://sea2.discourse-cdn.com/rubyonrails/user_avatar/discuss.rubyonrails.org/ahmad54/32/13431_2.png) [@ahmad54](https://discuss.rubyonrails.org/u/ahmad54)\
**Post date:** [June 8, 2025, 11:58am UTC](https://discuss.rubyonrails.org/t/write-only-fields-with-activerecord/89349/3 "2025-06-08T11:58:25Z")

</div>

you are right Tobias L. Maier

---

<div class="post-metadata">

**Author:** ![schmijos](https://sea2.discourse-cdn.com/rubyonrails/user_avatar/discuss.rubyonrails.org/schmijos/32/1623_2.png) [@schmijos](https://discuss.rubyonrails.org/u/schmijos)\
**Post date:** [July 9, 2025, 8:30am UTC](https://discuss.rubyonrails.org/t/write-only-fields-with-activerecord/89349/4 "2025-07-09T08:30:57Z")

</div>

[`readonly?`](https://api.rubyonrails.org/classes/ActiveRecord/Core.html#method-i-readonly-3F) and [`attr_readonly`](https://api.rubyonrails.org/classes/ActiveRecord/ReadonlyAttributes/ClassMethods.html#method-i-attr_readonly) are exactly the opposite of what I want. I’m searching for `writeonly?` and `attr_writeonly`. Is there a good reason why this doesn’t exist in Rails?

---

<div class="post-metadata">

**Author:** ![schmijos](https://sea2.discourse-cdn.com/rubyonrails/user_avatar/discuss.rubyonrails.org/schmijos/32/1623_2.png) [@schmijos](https://discuss.rubyonrails.org/u/schmijos)\
**Post date:** [November 17, 2026, 2:13pm UTC](https://discuss.rubyonrails.org/t/write-only-fields-with-activerecord/89349/5 "2026-11-17T14:13:53Z")

</div>

This could be a solution which doesn’t interfere too deeply.

```ruby
class Account < ApplicationRecord
  include WriteonlyEncryption

  attr_encrypt_writeonly :pin
end

```

Provided functionality with a module like that. It adds the getter and setter `#pin` and `#pin=`.

```ruby
module WriteonlyEncryption
  extend ActiveSupport::Concern

  class_methods do
    def attr_encrypt_writeonly(*names, public_key: Rails.application.credentials.writeonly_encryption_public_key)
      raise ArgumentError, "attr_encrypt_writeonly needs at least one attribute" if names.empty?
      raise ArgumentError, "attr_encrypt_writeonly needs a public key" if public_key.blank?

      sealer = RbNaCl::Boxes::Sealed.from_public_key(RbNaCl::PublicKey.new(Base64.strict_decode64(public_key)))
      self.filter_attributes += names

      names.each do |name|
        define_method(:"#{name}=") do |plain|
          super(plain.presence && Base64.strict_encode64(sealer.box(plain)))
        end

        define_method(name) do
          raise NoMethodError, "#{self.class}##{name} is write-only"
        end
      end
    end
  end
end

```
