I've created a PR for fixing: https://github.com/ory/hydra/issues/3137 It is very small change; a few characters in 1 line, which I believe is already covered by automated tests. However Codecov reports that it impacts 124 files and make the overall test coverage drop by 1,51% This does not seem right to me. anyone who can help me understand why I am getting this feedback?

Hi, I have a quick question on why there is a difference in Kratos on the ReturnTo depending on flows: On the login, if you're already logged-in, you get redirected to the propre ReturnTo URL: See here: https://github.com/ory/kratos/blob/master/selfservice/flow/login/handler.go#L353 Whereas on the Registration Flow, If you're already logged-in, you get redirected only to the default URL: See here: https://github.com/ory/kratos/blob/master/selfservice/flow/registration/handler.go#L252 I was wondering if it was by design, or it was a 'bug' ?

I think returnTo url should be honored anyway

Hey folks, I noticed there’s a lint error causing CI failures on kratos right now- I have a fix for it in an existing docs change PR I had open, but I’m happy to decouple it from my other changes if that’s preferable

awesome!

Yeah simple fix, but my PR is also not yet merged 😅

haha! Oh, I didn’t realize you had also fixed it 😁

Hey, we’d like some help with our PR on saml federation in Kratos. We hadn't updated kratos-selfservice-ui-node for a while and were still on the pink interface. Our SAML implementation is going well, and we had our own "Sign in with SAML" button. I should point out that at no time did we need to modify the ui-node code to have the button. Since we updated the ui-node on the last commit (we update regularly on Kratos too), we lost our SAML button, only the OIDC is here now. We implemented a PopulateLoginMethod method for SAML as well as you did for OIDC (strategy_login.go) and the populateMethod method (strategy.go) We also have our own AddProviders and AddProvider methods for SAML (types.go) in order to append the corresponding node to the container. At the end, the method NewInfoLoginWith (message_loging.go) is called for both OIDC and SAML. So could you give us a clue about why out “Sign in with SAML” button doesn’t appear anymore please? Have there been any changes, either on the kratos side or on the ui side that make it not enough for the button to appear anymore? We can't find it on our side. Thank you!

Hi guys I am new to this project and wanted to contribute to the ory/kratos project. I have cloned the repo locally but I can't run the migrate command:

go run ./main.go migrate sql -c ./tmp/config.yml -e

I get this error:

WARN[2022-11-14T22:02:24+05:30] Unable to connect to database, retrying.      audience=application error=map[message:could not create new connection: sqlite3 support was not compiled into the binary stack_trace:stack trace could not be recovered from error type *fmt.wrapError] service_name=Ory Kratos service_version=master

Can someone please help me out with this?

hi

can you try

make quickstart-dev

Hey, I'm coming back to you regarding our PR about the SAML federation (#2653). Your reviews have been taken into account, and we have finished the tests covering our continuity manager based on RelayState (essential to the SAML flow, more information here #2486). Could you please take a look at it and tell us what's missing on your side for the merge please? Additional note: we are currently writing our SAML vulnerability assessment tests to prove that our implementation covers them all. Merry Christmas to all, and happy new year! :)

@steep-lamp-91158 @gentle-thailand-50068

@high-optician-2097 Hello! Is it ok if I rebase this PR with the main branch and start working on where the previous author left off. We need this functionality along with account lock feature. I would like to contribute the account lock feature if that’s ok.

Hi if I want to contribute some idea or probable bug - is it preferable to create an issue with technical description and code referrals or pull request with implementation but without or minimal tests?

@limited-wire-43082 hello. It’s best to create an issue in the GitHub repo and request a review first from me or @high-optician-2097 . That makes it easier to follow tests and merge the subsequent PR

Hi all. New guy here. I’ve got a PR for Fosite and a matching one for Hydra. Currently, CI is failing conformity tests because it looks like it is trying to use my new change with the master version of Hydra. I’ve added a new field to fosite.Config so it is causing an error. Maybe I added it in the wrong places? I’m just getting used to this codebase. https://github.com/ory/fosite/pull/733

Hi @high-optician-2097 @magnificent-energy-493, With @faint-toddler-5440, we have made a proposal for specs for this issue: https://github.com/ory/kratos/issues/140 If you have any time please, we'd love to have your feedbacks and comments, Thanks in advance,

hey, is there a timeline on when community PRs get merged and end up in ory-network? specifically care about https://github.com/ory/kratos/pull/3088 thanks! 🙂

hey it’s on my list to review today and will be most likely live until EoW (unless something unexpected happens)

A small PR to improve the helm docs for oathkeeper 🙂 https://github.com/ory/k8s/pull/574

@high-optician-2097 @magnificent-energy-493 Finally updated our PR: https://github.com/ory/oathkeeper/pull/916 Seems like most was already implemented through others, but it's still adding a few test cases. Yay, or nay?

Oh, and a "fix" for empty subject. Which is more a wrong configuration thing, but really messy to debug when it happens.

Hi @magnificent-energy-493 @high-optician-2097. I made a PR for kratos to support importing peppered password hashes (related issue). I’d love to get your feedbacks and comments,

@high-optician-2097 @magnificent-energy-493 would Ory be open to contributions of newer KYC supporting extensions to oAuth 2.0 (specifically openid-4-verifiable-presentations-1_0) to Fosite/Hydra? Would there be any complications regarding status of the extensions etc. that would block you to merge it to the main branches?

Hi @high-optician-2097 I have made a PR for the Oathkeeper Rules schema, which addresses this issue. I'd like to hear your thoughts.

Hi there, unfortunately really busy this week. Will try next week!

Hi all, I created the following PR and the step format fails but Prettier locally does not find a format problem. Does anyone have any idea why?

📣 Anyone who wants to run Ory CLI in Github Actions and having troubles - I just published Github Action. Feel free to use it. Current implementation uses expect method, since Ory CLI does not support non-interactive auth (e.g.

ory auth --email <mailto:example@mail.com|example@mail.com> --password MyPassword

). I'll address this in the next PR of Ory CLI.