Re: [cas-user] How do to G Suite as a normal SAML SP?

[Richard Frovarp]

I've seen some of those. I guess the part that I'm struggling with is the 
values to enter. G Suite doesn't publish their end points. I can probably grab 
them using SAML Tracer and my existing working integration. I was more 
wondering if someone had a known working configuration so I don't have to guess 
and try multiple times.

On 3/5/20 1:51 PM, Ray Bon wrote:
Richard,

There are some online tools that can get you started, 
https://www.google.com/search?client=ubuntu=fs=saml2+create+metadata=utf-8=utf-8

Ray

On Thu, 2020-03-05 at 19:42 +, Richard Frovarp wrote:

I'm missing something basic in what it is that I need. We have G Suite

setup through the custom bit in CAS. That is conflicting with our other

normal SAML SPs and throwing stack traces. I see that in 5.3, the

version that we are on, the custom bit has been deprecated. What I'm not

able to wrap my head around is how to construct the SP metadata for G

Suite. Do I just monitor the URLs that are currently working to set the

end points? Or is there a better way to do this? I'm used to dealing

with systems that will give me their metadata, rather than having to

construct it.




Any help would be appreciated. Thanks,




Richard




--


Ray Bon
Programmer Analyst
Development Services, University Systems
2507218831 | CLE 019 | r...@uvic.ca

I respectfully acknowledge that my place of work is located within the 
ancestral, traditional and unceded territory of the Songhees, Esquimalt and 
WSÁNEĆ Nations.
--
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
---
You received this message because you are subscribed to the Google Groups "CAS 
Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cas-user+unsubscr...@apereo.org.
To view this discussion on the web visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/aba0e65d40c04a88839bece305353c2210a9b677.camel%40uvic.ca.

-- 
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
--- 
You received this message because you are subscribed to the Google Groups "CAS 
Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cas-user+unsubscr...@apereo.org.
To view this discussion on the web visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/5a3d170f-d0ff-4d07-8207-9c455f22828d%40ndsu.edu.

Re: [cas-user] How do to G Suite as a normal SAML SP?

[Ray Bon]

Richard,

There are some online tools that can get you started, 
https://www.google.com/search?client=ubuntu=fs=saml2+create+metadata=utf-8=utf-8

Ray

On Thu, 2020-03-05 at 19:42 +, Richard Frovarp wrote:

I'm missing something basic in what it is that I need. We have G Suite

setup through the custom bit in CAS. That is conflicting with our other

normal SAML SPs and throwing stack traces. I see that in 5.3, the

version that we are on, the custom bit has been deprecated. What I'm not

able to wrap my head around is how to construct the SP metadata for G

Suite. Do I just monitor the URLs that are currently working to set the

end points? Or is there a better way to do this? I'm used to dealing

with systems that will give me their metadata, rather than having to

construct it.


Any help would be appreciated. Thanks,


Richard


--

Ray Bon
Programmer Analyst
Development Services, University Systems
2507218831 | CLE 019 | r...@uvic.ca

I respectfully acknowledge that my place of work is located within the 
ancestral, traditional and unceded territory of the Songhees, Esquimalt and 
WSÁNEĆ Nations.

-- 
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
--- 
You received this message because you are subscribed to the Google Groups "CAS 
Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cas-user+unsubscr...@apereo.org.
To view this discussion on the web visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/aba0e65d40c04a88839bece305353c2210a9b677.camel%40uvic.ca.

[cas-user] How do to G Suite as a normal SAML SP?

[Richard Frovarp]

I'm missing something basic in what it is that I need. We have G Suite 
setup through the custom bit in CAS. That is conflicting with our other 
normal SAML SPs and throwing stack traces. I see that in 5.3, the 
version that we are on, the custom bit has been deprecated. What I'm not 
able to wrap my head around is how to construct the SP metadata for G 
Suite. Do I just monitor the URLs that are currently working to set the 
end points? Or is there a better way to do this? I'm used to dealing 
with systems that will give me their metadata, rather than having to 
construct it.

Any help would be appreciated. Thanks,

Richard

-- 
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
--- 
You received this message because you are subscribed to the Google Groups "CAS 
Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cas-user+unsubscr...@apereo.org.
To view this discussion on the web visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/376aee22-5c98-3e7e-4ac4-5e6c22d9e1f6%40ndsu.edu.