# Trouble signing CLA

**URL:** <https://discuss.elastic.co/t/trouble-signing-cla/376586>\
**Category:** Elastic Cloud on Kubernetes (ECK)\
**Created:** [March 31, 2025, 1:22pm UTC](https://discuss.elastic.co/t/trouble-signing-cla/376586 "2025-03-31T13:22:27Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![doralenart](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/doralenart/32/142342_2.png) [@doralenart](https://discuss.elastic.co/u/doralenart)\
**Post date:** [March 31, 2025, 1:22pm UTC](https://discuss.elastic.co/t/trouble-signing-cla/376586/1 "2025-03-31T13:22:28Z")

</div>

Hi Elastic Team!

I can't seem to get my CLA signature recognized for this PR: [KnownType links override KubeType links by doralenart · Pull Request #143 · elastic/crd-ref-docs · GitHub](https://github.com/elastic/crd-ref-docs/pull/143)

The commit has the email address I have on github. I also tried with different names (although I don't think that matters).

A possible issue: my email address wasn't public when I first created the PR. But I tried to resign since, without success.

Also, after signing (I can download the pdf), docusign throws a tantrum:

 ![Screenshot from 2025-03-31 14-58-08](https://us1.discourse-cdn.com/elastic/original/3X/3/e/3e0033643ed5284105dc4c05c4808e8783d3672b.png)

---

<div class="post-metadata">

**Author:** ![jessgarson](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jessgarson/32/129841_2.png) [@jessgarson](https://discuss.elastic.co/u/jessgarson)\
**Post date:** [March 31, 2025, 3:33pm UTC](https://discuss.elastic.co/t/trouble-signing-cla/376586/2 "2025-03-31T15:33:11Z")

</div>

Hi, @doralenart,

I have a follow-up question: what browser are you using? Has this issue occurred in multiple browsers?

Thanks!

Jessica

---

<div class="post-metadata">

**Author:** ![doralenart](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/doralenart/32/142342_2.png) [@doralenart](https://discuss.elastic.co/u/doralenart)\
**Post date:** [March 31, 2025, 5:31pm UTC](https://discuss.elastic.co/t/trouble-signing-cla/376586/3 "2025-03-31T17:31:44Z")

</div>

Chrome (that's where the first screenshot is from),  
Chrome mobile,  
Firefox:

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/9/a/9aa8b3c415cc6dea56438c4367f3e917b9e436c1.png)

(Firefox also complains about some CSP violation: `Content-Security-Policy: The page’s settings blocked the loading of a resource (frame-ancestors) at <unknown> because it violates the following directive: “frame-ancestors https://na3.docusign.net”`)

But I also tried saving the signing process and finishing it from docusign's own website (to avoid the whole iframe-hassle on Elastic's website).

Thanks 🙂

---

<div class="post-metadata">

**Author:** ![doralenart](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/doralenart/32/142342_2.png) [@doralenart](https://discuss.elastic.co/u/doralenart)\
**Post date:** [March 31, 2025, 6:12pm UTC](https://discuss.elastic.co/t/trouble-signing-cla/376586/4 "2025-03-31T18:12:06Z")

</div>

Hmm, I pushed some changes, and now the signature is accepted.

So either someone fixed something manually, or a new commit reruns the CLA check.

Thanks for your help!

---

<div class="post-metadata">

**Author:** ![jessgarson](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jessgarson/32/129841_2.png) [@jessgarson](https://discuss.elastic.co/u/jessgarson)\
**Post date:** [April 1, 2025, 10:03pm UTC](https://discuss.elastic.co/t/trouble-signing-cla/376586/5 "2025-04-01T22:03:44Z")

</div>

Glad you found a solution, @doralenart. I'll keep my eye out for similar issues as well.