ory / ory/sdk

Rust client fail to parse UiNodeAttributes

Open
#381 7 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
PHP
Stars
178
Forks
96
Avg merge
6d 23h
Merged PRs (30d)
3

Description

Preflight checklist
Ory Network Project

No response

Describe the bug

While using create_native_registration_flow, I ran into the following bug:

called `Result::unwrap()` on an `Err` value: Serde(Error("missing field `node_type`", line: 1, column: 508))

It seems to have occurred once before in https://github.com/ory/sdk/issues/325 and appeared again

Reproducing the bug

Run the following code:

use ory_client::apis::{
    configuration::Configuration, frontend_api::create_native_registration_flow,
};

#[tokio::main]
async fn main() {
    create_native_registration_flow(
        &Configuration {
            base_path: "http://localhost:4433".to_string(),
            ..Default::default()
        },
        None,
        None,
    )
    .await
    .unwrap();
}
Relevant log output
called `Result::unwrap()` on an `Err` value: Serde(Error("missing field `node_type`", line: 1, column: 508))
Relevant configuration

No response

Version

Kratos 1.3.0

On which operating system are you observing this issue?

macOS

In which environment are you deploying?

Docker Compose

Additional Context

docker image: oryd/kratos:v1.3.0
cargo:

ory-client = { git = "https://github.com/ory/client-rust", tag = "v1.14.5" }

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by running the provided Rust example with create_native_registration_flow against the stated Kratos and Docker Compose setup, then inspect how UiNodeAttributes is deserialized. Done means the registration-flow response parses successfully without the missing node_type error.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
api
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.