Skip to Content
0
Former Member
Feb 20, 2009 at 06:45 PM

openDocument not working with SSO

96 Views

I have configured InfoView SSO using Vintela on BO Edge 3.0 and it is working fine. I have reports using openDocument. I have searched this forum and found a reference to SAP note 1248492. Followed the resolution and it is failing with following error.

HTTP Status 404 - /ull

-


type Status report

message /ull

description The requested resource (/ull) is not available.

-


Apache Tomcat/5.5.20

The tomcat stdout reads:

[DEBUG] Fri Feb 20 10:42:04 PST 2009 jcsi.kerberos: decrypted ticket:

Ticket:

encryption type: 3 (DECRYPTED OK)

service principal: HTTP/boedgnvt01.bmrn.com("at")BMRN.COM

TransitedEncoding:

client: user"at"BMRN.COM

session key: [3, 37 31 3b d9 19 23 70 f1 ]

ticket flags: forwardable renewable ok-as-delegate preauthent

valid from: Fri Feb 20 10:42:04 PST 2009

valid till: Fri Feb 20 20:42:04 PST 2009

valid for:

all addresses

auth data:

[1, 30 82 3 9a 30 82 3 96 a0 4 2 2 0 80 a1 82 3 8c 4 82 3 88 4 0 0 0 0 0 0 0 1 0 0 0 f0 2 0 0 48 0 0 0 0 0 0 0 a 0 0 0 1e 0 0 0 38 3 0 0 0 0 0 0 6 0 0 0 14 0 0 0 58 3 0 0 0 0 0 0 7 0 0 0 14 0 0 0 70 3 0 0 0 0 0 0 1 10 8 0 cc cc cc cc e0 2 0 0 0 0 0 0 0 0 2 0 fe 5 f ed 8a 93 c9 1 ff ff ff ff ff ff ff 7f ff ff ff ff ff ff ff 7f 4a cf 58 28 6c 93 c9 1 4a cf 58 28 6c 93 c9 1 4a 4f 86 11 25 da c9 1 14 0 14 0 4 0 2 0 20 0 20 0 8 0 2 0 12 0 12 0 c 0 2 0 0 0 0 0 10 0 2 0 34 0 34 0 14 0 2 0 4 0 4 0 18 0 2 0 d8 2a 0 0 28 11 0 0 1 2 0 0 17 0 0 0 1c 0 2 0 20 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 e 0 10 0 20 0 2 0 10 0 12 0 24 0 2 0 28 0 2 0 0 0 0 0 0 0 0 0 10 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 2c 0 2 0 0 0 0 0 0 0 0 0 0 0 0 0 a 0 0 0 0 0 0 0 a 0 0 0 64 0 65 0 73 0 63 0 61 0 6d 0 69 0 6c 0 6c 0 6f 0 10 0 0 0 0 0 0 0 10 0 0 0 44 0 65 0 6e 0 6e 0 69 0 73 0 20 0 45 0 73 0 63 0 61 0 6d 0 69 0 6c 0 6c 0 6f 0 9 0 0 0 0 0 0 0 9 0 0 0 75 0 6e 0 69 0 76 0 33 0 2e 0 62 0 61 0 74 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1a 0 0 0 0 0 0 0 1a 0 0 0 5c 0 5c 0 65 0 6d 0 63 0 6e 0 6f 0 30 0 32 0 5c 0 75 0 73 0 65 0 72 0 73 0 5c 0 64 0 65 0 73 0 63 0 61 0 6d 0 69 0 6c 0 6c 0 6f 0 2 0 0 0 0 0 0 0 2 0 0 0 48 0 3a 0 17 0 0 0 a8 1d 0 0 7 0 0 0 86 e 0 0 7 0 0 0 21 9 0 0 7 0 0 0 4c 17 0 0 7 0 0 0 e2 8 0 0 7 0 0 0 4f 17 0 0 7 0 0 0 7d 28 0 0 7 0 0 0 72 22 0 0 7 0 0 0 1 2 0 0 7 0 0 0 e2 11 0 0 7 0 0 0 71 9 0 0 7 0 0 0 d5 9 0 0 7 0 0 0 86 c 0 0 7 0 0 0 5c 22 0 0 7 0 0 0 df 8 0 0 7 0 0 0 b2 1b 0 0 7 0 0 0 fe 17 0 0 7 0 0 0 5d 1c 0 0 7 0 0 0 c6 e 0 0 7 0 0 0 5e 1d 0 0 7 0 0 0 e6 a 0 0 7 0 0 0 a3 13 0 0 7 0 0 0 9 1b 0 0 7 0 0 0 8 0 0 0 0 0 0 0 7 0 0 0 44 0 43 0 4e 0 56 0 54 0 30 0 31 0 0 0 9 0 0 0 0 0 0 0 8 0 0 0 42 0 49 0 4f 0 4d 0 41 0 52 0 49 0 4e 0 4 0 0 0 1 4 0 0 0 0 0 5 15 0 0 0 3b 23 f5 57 9d 60 3 7b 71 45 54 0 1 0 0 0 30 0 2 0 7 0 0 20 5 0 0 0 1 5 0 0 0 0 0 5 15 0 0 0 3b 23 f5 57 9d 60 3 7b 71 45 54 0 8c 29 0 0 0 e6 89 ec 8a 93 c9 1 14 0 64 0 65 0 73 0 63 0 61 0 6d 0 69 0 6c 0 6c 0 6f 0 0 0 76 ff ff ff d8 ba ab 33 2b f2 af 51 34 b1 ba d8 2a 65 64 6c 0 0 0 0 76 ff ff ff d7 a1 8d 20 5a d3 93 8f 51 92 6 70 3a c9 1 8b 0 0 0 0 ]

[DEBUG] Fri Feb 20 10:42:04 PST 2009 jcsi.kerberos: Setting context expiry to [1235191324000]

[DEBUG] Fri Feb 20 10:42:04 PST 2009 jcsi.kerberos: Current wall time is [1235155324924]

[DEBUG] Fri Feb 20 10:42:04 PST 2009 jcsi.kerberos: ** decrypting application request .. **

with key

[3, 37 31 3b d9 19 23 70 f1 ]

[DEBUG] Fri Feb 20 10:42:04 PST 2009 jcsi.kerberos: decrypted application request:

++++ KRB-AP-REQ Message ++++

encryption type: 3 (DECRYPTED OK)

ap options: mutual-required

Ticket:

encryption type: 3

service principal: HTTP/boedgnvt01.bmrn.com"at"BMRN.COM

client: user"at"BMRN.COM

subkey: [3, 25 b6 52 f2 ba a4 d3 ea ]

client time: Fri Feb 20 10:42:07 PST 2009

cusec: 2332

sequence number: 1759111339

++++++++++++++++++++++++++++

[DEBUG] Fri Feb 20 10:42:04 PST 2009 jcsi.kerberos: ** creating application response .. **

with key

[3, 37 31 3b d9 19 23 70 f1 ]

[DEBUG] Fri Feb 20 10:42:04 PST 2009 jcsi.kerberos: created application response:

++++ KRB-AP-REP Message ++++

encryption type: 3

sequence number: 47830298

sub session key: null

client time: Fri Feb 20 10:42:07 PST 2009

cusec: 2332

++++++++++++++++++++++++++++

Any clues? It seems to be close!